I'm going to promote a server to a DC and install AD. I read here about the confusion re internal and external names. I understand I should give the internal one an extension of .local so DNS can understand it. But is it necessary that the first part of this name match what is our external name? I.e., we're not doing a website, we just have a domain name registered out there for email, which I think is long and cumbersome and would rather not use internally. So can I name my internal one abc.local and the one to be used just for email is blahblahblah.com?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Internal vs. external dns names
- Thread starter boryan
- Start date
GlenJohnson
MIS
If you don't currently have a domain setup internally, it will be called whatever you name it in Active Directory, unless you've already named it, in which case AD will call it what it is now. If the dc isn't going on the internet, call it what you want. Good luck.
Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
- Thread starter
- #3
I named it domainname.abc.local
But DNS won't resolve to that. And the reverse lookup won't resolve and has no in adda arpa listing. This server will eventually go out to the internet, but right now I'm just trying to get it to resolve internally. Hence the concern about which names to use internally vs. externally. Nslookup says it can't find the server and then the next line gives me the whole correct address: computername.domainname.abc.local
I'm confused here. I thought I knew how to do this.And the interesting thing is that I had named it internally with a .com suffix originally and everything worked. Then I kept reading that I need to name it with a .local suffix. So I went and fixed it by demoting and then promoting the DC. And now that I've got it at local, it's toast....
But DNS won't resolve to that. And the reverse lookup won't resolve and has no in adda arpa listing. This server will eventually go out to the internet, but right now I'm just trying to get it to resolve internally. Hence the concern about which names to use internally vs. externally. Nslookup says it can't find the server and then the next line gives me the whole correct address: computername.domainname.abc.local
I'm confused here. I thought I knew how to do this.And the interesting thing is that I had named it internally with a .com suffix originally and everything worked. Then I kept reading that I need to name it with a .local suffix. So I went and fixed it by demoting and then promoting the DC. And now that I've got it at local, it's toast....
GlenJohnson
MIS
1)Who said you needed .local?
2)Why not rename it with .com again and see what happens?
3)You said originally it was not going on the internet. Which is it? What are the final plans for the server?
Good luck.
Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
2)Why not rename it with .com again and see what happens?
3)You said originally it was not going on the internet. Which is it? What are the final plans for the server?
Good luck.
Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
- Thread starter
- #5
Some of the expert tipsters on this forum said that. So I'll try renaming it to .com and see if that works. What I originally tried to say was that this server is not currently connected to the internet cuz I want to get it up and running and working on its own before I make that connection, and also because of a logistical issue: I cannot connect it right now. But eventually it will have to connect for web access and to retrieve our emails.
I'm going to assume what's happening: This is a parent child domain design. (parent-> abc.local, child -> domainame.abc.local). First you have to create the parent and its dns becames the primary, then create the child and point it dns ip entry to your parent ip. Now what happens is that you're creating a child first.. then you'll have a DNS problem. Now if you can explain more then we don't have to assume here
.
.- Thread starter
- #7
You're incredibly helpful. But I just demoted my dc again,re-promoted it and started all over again, slowly, slowly, and it now works just fine, using abc.local. So now I'll reinstall AD and stop messing with it. I really do appreciate your taking the time to answer my questions. This forum can be so helpful when one gets a brain fade, and you all are so generous with your time and knowledge.
GlenJohnson
MIS
Don't wait to connect to the internet. You are going to need patches and fixes downloaded to make the server run correctly. Good luck.
Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question