Awaiting External DNS for a new Subdomain

I have a site registered with Godaddy just for the domain. I had a custom marketplace designed for some customers of mine. I am trying to point a new subdomain which is b2b to an IP address using an A record. I added the Namerservers to Godaddy but I am getting a awaiting external DNS. It says check your domains nameservers. I cant change any DNS records with godaddy because it I am using nameservers. I am not sure what to do.

  • We need to know your netlify site name. Example:
  • DNS issues? Tell us the custom domain, tell us the error message! We can’t help if we don’t know your domain.

If you want this to point to an external location not served by Netlify, then you should not add it to a Netlify site. is using Netlify DNS (as shown in the screenshot above) ergo any configuration of DNS records needs to happen via the Netlify DNS dashboard and not via GoDaddy. Check out this documentation on how to configure DNS records via Netlify.

I am going to type a really long message here. I bought my domain from but I am hosting with netlify who deploys my code from github. On godaddy I changed my name servers to netlify and so now netlify manages the DNS. I recently have brought on some customers that wanted a marketplace. I do not know back end and API’s so I had someone else code it for me and they are hosting it as a SaaS. They told me I need to add a sub domain like b2b and then add a A record with a specific IP address they gave me. Do I need to add the domain on the domains page or just add the DNS record? I am so lost. And I get netlify being free but crap if they really want more customers to pay they should have at least someone answer the phone and say yeah go here. Because searching the forums when you dont actually know wtf youre looking for is like looking for a needle in a haystack except someones playing a trick on you and there isnt a freaking needle at all. Its just another piece of hay.

Also I am not sure who flagged me for advertising but this platform cannot be used by the public. I dont want any of you using it. It is for one customer inside the goverment so not sure what jackwagon flagged it but thats really nice I am trying to get help and some keyboard jockey flagged it. real mature. really nice community too. A new developer is trying to get help and thats how hes treated. nerds with no life.

You only add the DNS record. You do not add it is a custom domain to the Netlify site.

In any event I see no records for

I have a A record I added. I can screen shot if you would like.

Hi, @John-Pratt. I’m only going to warn you once:

  • Do not be rude to anyone here on this support forum.

I’m talking about comments like this:

and this:

First, it was an automated system that flagged your post not a person. Second, even if someone had flagged the post, name-calling is not an appropriate way of handling issues. If you are rude again you will be blocked from posting in this support forum.

When you added the domain to the site’s custom domain settings it created a NETLIFY type DNS record as shown below:

This is causing an issue because NETLIFY records and A records for the same domain name are incompatible. This means that the A record isn’t working yet. These are the steps to resolve this:

  1. Remove the domain from the site’s domain management settings.
  2. On the settings page for the domain (not the site) delete both the NETLIFY and NETLIFYv6 records for
  3. Delete the A record for as well (which may seem counter-intuitive but is is required).
  4. Add the A record for back again.

At that point, the A record will work correctly. If it does not or if there are any questions, please let us know.

1 Like

So you are saying it needs to look like this below for it to work? Sorry I was frustrated. It said community so I thought someone did it because they thought I was advertising. Does this look correct?

That’s correct @John-Pratt and the record has propagated

$ dig	67	IN	A