Unable to (randomly) resolve hostname on ns7/ns14

[Steve Williams]

Hi,

My domain "williamsitconsulting.com" has 2 dynamic addresses being updated, williamsitconsulting.com and www .williamsitconsulting.com.

I also have MX records being served up statically.

I have 2 DNS servers configured,

• ns14.zoneedit.com
• ns7.zoneedit.com

For several weeks, there have been different IP addresses being served for my domain from the 2 different DNS servers. I was in South America on vacation and unable to deal with it. I am home now, and as of yesterday, it seems that my domain is not being resolved at all now, or perhaps on a random basis.

I have another domain williams-steve.com that is being served by ns9/13 and it's working flawlessly.

I have re-run my dynamic updater script and it doesn't seem to make a difference. My domain appears and disappears on a random basis (resolve/not resolve).

How can we get this problem resolved?

Thanks,
Steve Williams

 

[Steve Williams]

I wrote a quick script to test the availability... All times are MST

Wed, Jan 04, 2017 12:51:18 PM

Pinging www williamsitconsulting.com [208.94.28.210] with 32 bytes of data:
Reply from 208.94.28.210: bytes=32 time=67ms TTL=240
Reply from 208.94.28.210: bytes=32 time=68ms TTL=240

Ping statistics for 208.94.28.210:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 68ms, Average = 67ms
Wed, Jan 04, 2017 12:51:49 PM

Pinging www williamsitconsulting.com [208.94.28.210] with 32 bytes of data:
Reply from 208.94.28.210: bytes=32 time=69ms TTL=240
Reply from 208.94.28.210: bytes=32 time=67ms TTL=240

Ping statistics for 208.94.28.210:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 69ms, Average = 68ms

Wed, Jan 04, 2017 12:52:20 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.

Wed, Jan 04, 2017 12:52:50 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:53:20 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:53:50 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:54:20 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:54:50 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:55:20 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:55:51 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:56:21 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:56:51 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:57:21 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:57:51 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.
Wed, Jan 04, 2017 12:58:21 PM
Ping request could not find host www williamsitconsulting.com. Please check the name and try again.

Wed, Jan 04, 2017 12:58:51 PM

Pinging www williamsitconsulting.com [208.94.28.210] with 32 bytes of data:
Reply from 208.94.28.210: bytes=32 time=68ms TTL=240
Reply from 208.94.28.210: bytes=32 time=67ms TTL=240

Ping statistics for 208.94.28.210:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 68ms, Average = 67ms

 

[sandy]

Hi Steve

two things.... for the ddns records.. you really do not need the record for www. normally that would be done in a Cname where www.williamsitconsulting.com points to williamsitconsulting.com

can you please change the nameservers delegated to the domain at the registrar and inside the zone file to be:
dns1.zoneedit.com
dns2.zoneeedit.com

while ns7 is investigated.

thanks and sorry for the inconvenience.

sandy

 

[Steve Williams]

Hi,

Thanks for the prompt reply.

I have changed my DNS Servers with my registrar as well as updating them on the zoneedit panel.

That's a great idea about using a CNAME. I do that for tons of things for my clients but never really thought about it for my own purposes!

I'm curious to see how long it takes for the DNS changes to propogate.

Cheers,
Steve W.

 

[sandy]