New DNS, certain ISP's won't resolve domains after weeks

OrganicOne

OrganicOne

one-legged douche burger
Apr 25, 2008
160
3
0
Michigan
I recently setup my own DNS at my domain register (Moniker), for use with a VPS. The new DNS is something simple like ns1.domain.com, and ns2.domain.com. This seems to work great for certain ISP's (mine included), however since moving to the VPS, all my sites have seen a drop in traffic.

More recently, I discovered that certain ISP's (Comcast, RoadRunner, and a few others), do not properly resolve the domain. I know they normally recommend waiting a few days for everything to propagate, but this has been weeks (even months on 1 of the domains).

Calling Moniker didn't seem to help much, as they told me its setup properly. Again, I have no issue while checking the sites using my internet provider, it just numerous other ones that seem to have issues. Has anyone else had this problem when setting up a new DNS? Any solution?
 


Did you actually register ns1.domain.com and ns2.domain.com as 'nameservers', it won't work if all you do is add an A record to those subdomains you actually have to register them as nameserves and point them to the IP addresses of your DNS server.
 
Yes, I used the "Create DNS" link in my moniker control panel, and pointed them to an IP address. Again, this seems to work with some ISP's, just certain ones don't seem to acknowledge it.

On a side note, they are both pointing to the same IP; not sure if this would cause them to ignore it or not....
 
Switch to an external DNS service and see if that work for you.
 
Pretty odd, however I've never used Moniker for anything domain related. It sure sounds like something isn't set up right. Are you using a domain with an extention outside of the big three (.com, .net, .org)? This same thing happened to me when trying to setup a .info as a nameserver.
 
OrganicOne said:
Yes, I used the "Create DNS" link in my moniker control panel, and pointed them to an IP address. Again, this seems to work with some ISP's, just certain ones don't seem to acknowledge it.

On a side note, they are both pointing to the same IP; not sure if this would cause them to ignore it or not....
Click to expand...

Create DNS is just gona create A records for your domain at Moniker's DNS server it will not create actual nameserver registrations. You need to explicitly register "nameservers" if you're trying to make your own private nameserver (ie: ns1.yourodmain.com).

Under namecheap its "Nameserver Registration" under Advanced Options

Under Godaddy its the "Host Summary" box in the very bottom left corner of a domain's advanced details.

The other ISP are likely ignoring your private nameservers provided in the WHOIS because they return "Non-Authoritive" if you didn't actually register them as nameservers.
 
This is where you set it up at moniker.....

Login to Moniker
Click "My Domains"
Put a check next to the domain
Click "DNS"
Click "Manage Name Server Host Records"

Is that what you already did?
 
johu said:
I meant switch to an external nameserver service - A free one that I've used is Free DNS, Static DNS, Dynamic DNS, URL Redirection, and more from EveryDNS! , and you just duplicate your zone entries (A records, CNAME, MX) there and point your domain to EveryDNS's nameservers.
Click to expand...

Im sure this would work, but I am still trying to figure out what I have done incorrectly (if anything).

kblessinggr said:
Create DNS is just gona create A records for your domain at Moniker's DNS server it will not create actual nameserver registrations. You need to explicitly register "nameservers" if you're trying to make your own private nameserver (ie: ns1.yourodmain.com).

Under namecheap its "Nameserver Registration" under Advanced Options

Under Godaddy its the "Host Summary" box in the very bottom left corner of a domain's advanced details.

The other ISP are likely ignoring your private nameservers provided in the WHOIS because they return "Non-Authoritive" if you didn't actually register them as nameservers.
Click to expand...

I dont see an option like this in Moniker, just Create DNS and "Manage Name Server Host Records", which both bring you to the same place. They both show the nameservers pointing to an IP. Whats even more odd is I tried to point a domain registered at 1and1, and it wont accept the nameservers. Moniker and Namecheap have no problems accepting the NS, it just only seems to work on about half of the ISP's I have tried.

Netphase said:
This is where you set it up at moniker.....

Login to Moniker
Click "My Domains"
Put a check next to the domain
Click "DNS"
Click "Manage Name Server Host Records"

Is that what you already did?
Click to expand...

Yup.

mguindon10 said:
Go here DNSstuff and put your "nameserver" domain in and see if it comes up in their whois lookup tool.
Click to expand...

DNSStuff shows the correct nameservers listed for the domains. :confused:
 
I signed up for the free account at DNSStuff to use their advanced tools.

I checked a domain that I have on another server, not using those nameservers, and received no errors.

Checking a domain that used the problematic nameservers gives me this:

Glue at parent nameservers: Warning
WARNING. The parent servers (I checked with d.gtld-servers.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.

All nameservers report identical NS records: Warning
WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).

Lame Nameservers: Failed
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated.

Missing Nameservers 2: Failed
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers.

Stealth NS Record Leakage: Failed
This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.

It also goes on to complain about both nameservers using the same IP, which is an easy fix. As for the other errors, not sure how to go about fixing those.
 
OrganicOne said:
Rage9: Im using a .org, forgot to mention this is the previous post.
Click to expand...
I'm not sure if .org would give you any troubles, with Namecheap I have used .com and .net with no problems.

I use intodns.com to check my nameservers.

However the messages you are getting are typical with it just not being set up right. Either a) your registrar sucks balls at namerservers, b) you can't set a .org as a nameserver (try with a .com or .net) or c) I have no real clue because after about 24-48 hours you should be fully good to go (assuming it's set up right).

Try with another registrar like Namecheap and see if it works. Kind of a pain in the ass but who knows.
 
You must log in or register to reply here.
Top Bottom