0

This is embarrassing, but I'm hoping the hive can point me somewhere on this one.

I've got a domain that until recently pointed to an internally hosted site. Almost immediately prior to my taking over this position, that site was moved to managed hosting and given a new domain name (actually moved to a subpage on a different domain).

Here is my problem: Anyone using our internal DNS cannot get to the site using the old domain name, but external users can.

I've tried creating an ALIAS, and that did not work. Should I delete the whole DNS Scope now that it is off prem?

Does anyone else have any ideas?

Thanks in advance, and I'm sorry for the dumb question

P.S. I basically did this if that helps: https://www.youtube.com/watch?v=j9UysIvo1W8

The DNS is not split.

Edited to put the correct video in

Jeffrey Bowers
  • 1
  • 1

2 Answers2

1

It sounds like your internal DNS server has that domain configured on it, so the local DNS will consider itself authoritative for any requests it receives locally, whereas anyone external would query the public DNS servers.

If that's the case you likely have two options.

  1. Replicate those new DNS records that have been setup for the new hosting on your local DNS server, so the records point to the correct destination. So for instance add the DNS records and subdomain used by the public website.

  2. If that zone isn't used internally, for instance it's NOT the domain you use for your local AD, and has only been setup locally for that old website, and it doesn't hold any records pointing to internal resources that are still in use, then you could consider simple deleting the zone from within your local DNS server. That would make your local DNS server no longer consider itself authoritative for that domain, and it would then look to the public internet to find the answer to any requests for that domain, therefore directing internal users to the correct public IP.

Note, before attempting option 2 I'd check very carefully that nothing internal still uses it (if need be, turn on debug logging in DNS so you can see what is being requested from it), and make sure you have backups/exports/records of what was there previously in case you need to put it back later.

Keith Langmead
  • 857
  • 1
  • 7
  • 14
  • Yeah, I'm scared of option two even if there don't seem to be anything else in that zone. How would I go about option 1? Given the nature of the hosting, I can't create an A Record. – Jeffrey Bowers Aug 22 '23 at 19:59
  • If the domain in question is configured in your local DNS then you just create an A record in there as required to point to where the website is. Eg, if that's the case, you basically have to copies of that DNS zone, one public and one local, with zero connection between the two. You need to update the local zone to make it match (at least in regard to the website in question) the DNS records in the public zone. – Keith Langmead Aug 22 '23 at 20:48
  • To expand slightly on Keith's comment: you have an on-premises DNS server, probably in an AD server or your router, and that's the one you need to change to match the public zone. – tsc_chazz Aug 22 '23 at 21:27
0

If the record is your local domain; like; example.com and example.com is your zone.

That would mean you can't erase the record or make a change easilly, but you could make it easy by configuring a www.example.com record that point to the external website, and to create on the DC that answer for example.com a local IIS that would do a example.com -> www.example.com 301 redirect.

yagmoth555
  • 16,758
  • 4
  • 29
  • 50