NAME SERVERs Problem

[mrd]

I have a reseller account. About a week ago I created Name Servers using two IP’s. It took a few days before I was able to access user account website http://mrdtrips.com I assigned to these NS. However, a day later I could not access this website. Today I am able to access it…

My other websites on this Reseller Account, assigned to my Web Host NS’s have been working OK over that time.

Why it is happening, on and off, with the domains assigned to NS1.MRDDATA.COM and NS2.MRDDATA.COM? Is it due to inconsistency in NS IP addresses shown in the records of different DNS servers (saved reports: http://mrddata.com/reports/name_server_problem.htm) or some other reasons? What should be done to fix it?

ns1.mrddata.com. [66.227.109.113] [TTL=172800] [US]
ns2.mrddata.com. [66.227.104.52] [TTL=172800] [US]

ns1.mrddata.com. A IN 14400 66.78.51.129
ns2.mrddata.com. A IN 14400 66.78.51.130

More details: http://mrddata.com/reports/name_server_problem.htm)

 

[thuskey]

Registering a new domain name and changing the nameserver addresses often take up to 96 hours for intenet wide population. What you discribe is normal.

As for the name server thing, it stopped with a failure due to ns1.mrdtrips.com and ns2.mrdtrips.com not existing, which is also normal.

what I am noticing is that ns1.mrddata.com is not responding. If it is a seperate server than ns2.mrddata.com then the named service may not be running, or port 53 is not being allowed in iptables.

if it is on the same server as ns2.mrddata.com, run a ifconfig to verify the ip address is correct, run a netstat -an to verify that all ip addresses are running port 53 named service, and check iptables -L to verify the default policy is either ACCEPT or traffic destined to port 53 is allow.

PM me if you need assistance with this task.

 

[nobaloney]

This is a response to mrd...

dnsreports fails for me as well, but when I dig your servers directly myself, up from the root, for mrdtrips.com, it works fine.

My well-educated guess is that you do not have great connectivity; either your connectivity is spotty to certain areas of the 'net, or to all areas of the 'net.

Since I have no problem finding your server, there's nothing I can do to help trace any network problems. You'll have to find someone who's having trouble (perhaps you) to contact your provider to do some tracing.

Jeff

 

[mrd]

Thanks for your help.

I’m not an expert in this area, but I believe that there are two records on different servers with the same Name Servers but different IP addresses and that’s the reason of the problem.

Incorect: [These were obtained from a.gtld-servers.net]
ns1.mrddata.com. [66.227.109.113] [TTL=172800] [US]
ns2.mrddata.com. [66.227.104.52] [TTL=172800] [US]
Correct:
ns1.mrddata.com. A IN 14400 66.78.51.129
ns2.mrddata.com. A IN 14400 66.78.51.130

I tried to connect to mrdtrips.com from different geographical locations (in San Francisco) and each time got the same pattern.

1. Unsuccessful HTTP to mrdtrips.com
2. Unsuccessful ping to mrdtrips.com, ns1.mrddata.com, ns1.mrddata.com (several attempts)
3. Successful ping to ns1.mrddata.com, ns2.mrddata.com
4. Successful ping to mrd.mrdtrips.com
5. And, finally, successful HTTP to mrdtrips.com

I cannot, however, expect every user, after first unsuccessful attempt, to follow this pattern in order to access my websites.

I believe that in order to stop routers confusions the Name Server records should be “manually” updated at whatever the place is:
from
ns1.mrddata.com. [66.227.109.113] [TTL=172800] [US]
ns2.mrddata.com. [66.227.104.52] [TTL=172800] [US]
[These were obtained from a.gtld-servers.net]
Reference: http://www.dnsreport.com/tools/dnsreport.ch?domain=mrdtrips.com
to
ns1.mrddata.com. [66.78.51.129] [TTL=172800] [US]
ns2.mrddata.com. [66.78.51.130] [TTL=172800] [US]
As configured with a DirectAdministration Reseller Panel

Please let me know if my thinking is correct, and what the next step should be.