1

I have Active Directory 2012 running (just got it running like today) and I chose the domain "markonsolutions.com"

I now noticed that when i try to visit www.markonsolutions.com that dns doesn't know what to do with it.

my questions

1) is this a bad practice to name our internal domain the same as our internet domain (my intention was to simplfy my users lives by giveing them the same log on as there email addresses)

2) If its not a big deal to have them both under the same name How can I add www or any of my other sub domains to go out to the internet dns?

Thanks

Improve this question
1

1 Answer 1

Reset to default
6

Q: Is this a bad practice to name our internal domain the same as our internet domain?

A: Yes it is.

Q: If its not a big deal to have them both under the same name How can I add www or any of my other sub domains to go out to the internet dns?

A: Don't go down that road. Either rename the current domain or wipe it and start from scratch using an unused sub-domain, such as ad.markonsolutions.com.

EDIT:

Statement: "my intention was to simplify my users lives by giving them the same log on as their email addresses"

Retort: Set up a UPN suffix that matches the DNS suffix of the email address and configure that for your users. This will wind up matching the parent DNS suffix of your AD FQDN if you name your domain something like ad.markonsolutions.com (the UPN suffix will be markonsolutions.com).

Improve this answer
12
  • Thanks for the simple answers. So If i did AD.markonsolutions.com. would my users still be able to log on as [email protected]?
    – Crash893
    Aug 26, 2013 at 20:54
  • See my edit....
    – joeqwerty
    Aug 26, 2013 at 20:55
  • 2
    The NetBIOS (down-level) logon would be AD\jdoe. The UPN logon would be [email protected]. If you create a UPN Suffix for markonsolutions.com then you can set the UPN logon to be [email protected]. That was the originally intended purpose for the UPN, but it never really caught on.
    – joeqwerty
    Aug 26, 2013 at 21:11
  • 1
    Technically, the NetBIOS name can be any allowed NetBIOS name, doesn't have to match any part of the DNS FQDN
    – mfinni
    Aug 26, 2013 at 21:18
  • 2
    Because nothing prevents .AD from being registered as a TLD in the future.
    – mfinni
    Aug 27, 2013 at 2:06

Not the answer you're looking for? Browse other questions tagged .