iMac can't find primary nameserver

Question

b0bTX Author

Level 1

4 points

iMac can't find primary nameserver

iMac connects to Time Capsule via WiFi.

Time Capsule connects to internet via Ethernet connection to Adtran router.

DHCP configures iMac Nameserver 10.0.1.1 (Time Capsule).

Time Capsule is configured with primary name server 198.6.1.5 (uu.net), secondary name server 198.6.100.38 (uu.net).

From the Adtran, I can ping 198.6.1.5, but ping packets from the iMac time out.

I can ping 198.6.100.38 from the iMac.

198.6.1.5 has worked for 4+ years.

I'm in the process of changing the name servers, but wondered if anything like this has ever been seen.

Posted on Aug 24, 2020 5:39 PM

Reply

Answer 1

Best reply

BDAqua

Level 10

239,777 points

Aug 24, 2020 7:12 PM in response to b0bTX

Make a New Location, Using network locations in Mac OS X ...

System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.

System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.

The interface that connects to the Internet should be dragged to the top of the list.

Sys Prefs>Network>highlight the Interface you're using>Advanced>TCP/IP>Configure IPv4: Using DHCP.

If using Wifi, instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.

System Preferences>Network>choose interface>Advanced>Proxies Tab, make sure none are set, like for HTTP & HTTPS.

System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...

8.8.8.8

8.8.4.4

1.1.1.1

9.9.9.9

Apply.

Reply

Answer 2

b0bTX Author

Level 1

4 points

Aug 26, 2020 4:07 PM in response to b0bTX

Thank you for your timely response and suggestion. I didn't bother creating a new location as you suggested, because it's all going to be changing within 7 - 10 days; this was initiated yesterday, and confirmed today.

The problem is that the client's contract with Verizon expired, so they opted to continue on a month - to - month basis. Verizon, in return degraded their service. A new agreement with a new ISP has been negotiated and is being implemented. The uu.net servers, owned by MCI were recommended at the onset of the Verizon agreement. The inability to contact the server at 198.6.1.5 is apparently a symptom of the degraded service. I try to avoid using anything Google (just personal preference), but I was able to ping 8.8.8.8, so added it as secondary name server. I will have to reconfigure everything within the next 2 weeks, so I have implemented workarounds to get them by in the interim.

Thanks!

Reply