Getting a 'No DNS Server' error on AirPort Time Capsule

I recently got a second-hand Airport Time Capsule and decided to use it as my home network router. Replaced my TP-Link router with the AirPort TC.


So here is my setup: I have a Fibre Optic Modem/Converter that acts as a optic-to-ethernet converter. I just put the ethernet cable on the WAN port of the AirPort TC, did the setup on my iPhone, skipped the PPPoE part and just let it run on DHCP & Nat. It gave a few errors relating to Double NAT but I ignored them.


It ran well for a day - nice speed and performance. But after that it showed me a bunch of errors starting with 'No DNS Server' and then PPPoE Server and No Internet Connection.


Here is everything I tried:

  1. Soft Reset
  2. Hard Reset
  3. Using the PPPoE login credentials but it still says they are incorrect
  4. Setting up a DNS Server (8.8.8.8 & 8.8.4.4. - something I saw others do on a forum)
  5. Updating Firmware





Nothing seems to work. What am I getting wrong?

The Router worked well for a day. Did I mess up a setting?

Time Capsule

Posted on Mar 2, 2025 4:36 AM

Reply
Question marked as Top-ranking reply

Posted on Mar 2, 2025 6:22 AM

Unfortunately, AirPort Utility for iOS is not really the same application as AirPort Utility for the Mac.


Do you have a Mac that you could use for the setup?


You should not have a Double NAT error if the Time Capsule is set up correctly, but AirPort Utility for iOS does not detect the type of signal that it is receiving from an upstream device all that well.....while AirPort Utility for Mac will normally work much better in this regard.


We want to avoid that Double NAT if at all possible, because ignoring a problem does not make it go away.

14 replies
Sort By: 
Question marked as Top-ranking reply

Mar 2, 2025 6:22 AM in response to Aditya1505

Unfortunately, AirPort Utility for iOS is not really the same application as AirPort Utility for the Mac.


Do you have a Mac that you could use for the setup?


You should not have a Double NAT error if the Time Capsule is set up correctly, but AirPort Utility for iOS does not detect the type of signal that it is receiving from an upstream device all that well.....while AirPort Utility for Mac will normally work much better in this regard.


We want to avoid that Double NAT if at all possible, because ignoring a problem does not make it go away.

Reply

Mar 3, 2025 9:03 AM in response to Aditya1505

Post back if you want to try DHCP Only mode and we'll go through the manual setup with you.....but the only reason to do this would be if you want the Time Capsule to be in charge of handing out IP addresses to all of your network devices.


Other than personal preference, there is no need to set up the Time Capsule this way.



Reply

Mar 2, 2025 8:13 AM in response to Aditya1505

Should I try a Static IP instead of Double NAT?


No, that won't help at this time.


Static IP would help if you were using a Router Mode of "DHCP Only", which is a very rarely used type of setup on the Apple AirPort routers. Apple never officially supported this type of setup.

Reply

Mar 3, 2025 6:11 AM in response to Aditya1505

Since the fibre optic modem is just a modem


The giveaway was your initial statement that you were seeing a Double NAT error when you initially set up the Time Capsule as a router.


The device that you call your "modem" is not really a modem. It is actually a simple router because it is providing DHCP and NAT service.


Since your "modem" was really a router "upstream" from the Time Capsule, the correct setting for the Time Capsule would be Bridge Mode.


But, there might be a question as to how many IP addresses the Fibre Converter can provide to the devices on your local network. If you are running out of IP addresses, there is a way to set up the Time Capsule to provide DHCP service......(but not NAT....which would create another Double NAT situation)......by setting up the Time Capsule to use a Router Mode of DHCP Only.


This can get complicated, because it requires some manual settings, and as I mentioned before Apple does not officially support this type of setup.


If everything is working OK now, I would leave well enough alone.

Reply

Mar 3, 2025 8:07 AM in response to Bob Timmons

Oh wow, that was stupid of me to not realise before. Thank you for taking out the time to understand and reply to my query. Saved me a visit to the Apple Store.


as per the fibre optic router giving out IP addresses, I haven’t had any issues with my previous TP Link router when it was connected to it. I did try ‘DHCP Mode Only’ before switching to Bridge Mode, it didn’t work out. I might try it again but as you said if it’s working, why bother changing. Also I am scared I might mess it up in some other way.


Thank You so much, Bob!

Reply

Mar 3, 2025 1:51 AM in response to Bob Timmons

Just tried this right now and surprisingly initially it showed the same error so I was about to give up. Let it sit on the network for a few mins and suddenly it showed internet is up and working. No more errors. Fingers crossed 🤞


So what was I getting wrong? Since the fibre optic modem is just a modem, how does the Airport TC work in bridge mode? Doesn't it need to configure DHCP?

Reply

Mar 3, 2025 10:44 AM in response to Bob Timmons

Ok something weird just happened - at 12:00 AM exact, The Internet went down. No error messages on AirPort Utility. So I simply switched the TC off and then on again. Gave it a few mins and the internet was back. However, the IP Address for the Router seems to have changed.


What's up with that? Is this the Optic Fibre router assigning new IP addresses every day? Should I go for a static IP in bridge mode? Not sure if this was an anomaly but I will see if this happens tomorrow midnight too.

Reply

Mar 3, 2025 2:33 PM in response to Aditya1505

Is this the Optic Fibre router assigning new IP addresses every day?


Appears to be the case based on your report. Normally a router will assign the same IP address to a device though that has already been assigned. It simply "renews" the same IP address, not changes it.


Should I go for a static IP in bridge mode?


Worth a try, but the trick will be to get into the settings on your Fibre router and have it assign a Static IP Address to the Time Capsule.


Yes, you can configure the Time Capsule using AirPort Utility to "request" a Static IP Address, but that assumes that the Fibre router will honor that request......and if it is automatically changing things at midnight.....it may try to change the "static" address that the Time Capsule is requesting.



Reply

Mar 3, 2025 5:28 PM in response to Bob Timmons

This might be a situation where OP wants to actually consider PPPoE - configuring the fiber modem to use PPPoE Passthrough (which is roughly equivalent to a Bridge Mode for a fiber modem), and then configuring the TC to be the router.


The specifics of how to do that can be modem model-dependent and need the assistance of their ISP Tech Support, though.

Reply

Mar 3, 2025 6:51 PM in response to Bob Timmons

Not sure who their ISP is of course, but I don't know of any fiber modem or converter that can make an ISP connection without a PPPoE username and password. Usually that's provided or provisioned by the ISP when the technician installs the device. I know I had to get those from my ISP to use PPPoE passthrough on my modem.


I did see where the OP indicated they tried it and had errors - but couldn't tell if they actually had the right credentials from their ISP.


Again, ISP dependent, but in my experience most ISP now are providing all-in-one fiber modem/router/wireless AP devices like Hitron Homehub models (and then renting additional wifi extenders as well as cable set-top boxes).

Reply

Getting a 'No DNS Server' error on AirPort Time Capsule

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.