Override DNS Record

When we have users on our guest wireless, they use our internal DNS, but
have no other access to our network resources. This leads to a problem when
they try to access webmail, or FTP since it resolves to our internal
address, rather than having them use our address over the internet.

So is there some way we can "override" the DNS addresses for certain hosts?
Something like assigning a host record through DHCP?

Thanks,
Brian

"Brian" <reply2me@thenewsgroup> wrote in message
news:...
> When we have users on our guest wireless, they use our internal DNS, but
> have no other access to our network resources. This leads to a problem
> when they try to access webmail, or FTP since it resolves to our internal
> address, rather than having them use our address over the internet.
>
> So is there some way we can "override" the DNS addresses for certain
> hosts? Something like assigning a host record through DHCP?
>
> Thanks,
> Brian
>

It's not an "override" rather that you have to make additional records
internally to make it work. For example, if your internal AD DNS domain name
is the same as the external name, you have to add a record internally that
is the same as the external name (such as "webmail") and provide the
internal IP. If the name is different, then you have to add the external
name zone on your internal DNS, add the "webmail" A record, and provide the
internal IP address.

Read more on it my blog, link below. I hope you find it helpful.

Split Zone or no Split Zone - Can't Access Internal Website with External
Name
http://msmvps.com/blogs/acefekay/arc...rnal-name.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"Ace Fekay [MCT]" <> wrote
> It's not an "override" rather that you have to make additional records
> internally to make it work. For example, if your internal AD DNS domain
> name is the same as the external name, you have to add a record internally
> that is the same as the external name (such as "webmail") and provide the
> internal IP.

I'm not sure how applicable this is, but that does describe our problem. I
have a DNS entry for webmail.domain.com with an IP on our internal network.
However the guest users need the external IP.

Brian

"Brian" <reply2me@thenewsgroup> wrote in message
news:...
> "Ace Fekay [MCT]" <> wrote
>> It's not an "override" rather that you have to make additional records
>> internally to make it work. For example, if your internal AD DNS domain
>> name is the same as the external name, you have to add a record
>> internally that is the same as the external name (such as "webmail") and
>> provide the internal IP.
>
> I'm not sure how applicable this is, but that does describe our problem. I
> have a DNS entry for webmail.domain.com with an IP on our internal
> network. However the guest users need the external IP.

Can't have it both ways. Guest will have to be on a different network with
a different DNS that resolves as you want it to be,...unless you want to
statically set the guest DNS and then "un-set" it before they leave. You
can statically set the DNS and still use DHCP for the rest.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Phillip Windell" <> wrote in message
news:%...
> "Brian" <reply2me@thenewsgroup> wrote in message
> news:...
>> "Ace Fekay [MCT]" <> wrote
>>> It's not an "override" rather that you have to make additional records
>>> internally to make it work. For example, if your internal AD DNS domain
>>> name is the same as the external name, you have to add a record
>>> internally that is the same as the external name (such as "webmail") and
>>> provide the internal IP.
>>
>> I'm not sure how applicable this is, but that does describe our problem.
>> I have a DNS entry for webmail.domain.com with an IP on our internal
>> network. However the guest users need the external IP.
>
> Can't have it both ways. Guest will have to be on a different network
> with a different DNS that resolves as you want it to be,...unless you want
> to statically set the guest DNS and then "un-set" it before they leave.
> You can statically set the DNS and still use DHCP for the rest.
>


Agreed.

Ace

"Phillip Windell" <> wrote
> Can't have it both ways. Guest will have to be on a different network
> with a different DNS that resolves as you want it to be

Drat. Oh well. I guess I can have DHCP assign them the external DNS. That
will solve the problem.

"Brian" <reply2me@thenewsgroup> wrote in message
news:%23%23OlQi$...
> "Phillip Windell" <> wrote
>> Can't have it both ways. Guest will have to be on a different network
>> with a different DNS that resolves as you want it to be
>
> Drat. Oh well. I guess I can have DHCP assign them the external DNS. That
> will solve the problem.

Sure, as long as it's a separate DHCP scope for the Guest network. You
wouldn't want to assign an external DNS for the internal machines, or you
will have numerous issues with AD.

Ace

"Ace Fekay [MCT]" <> wrote
> Sure, as long as it's a separate DHCP scope for the Guest network.

It is.

Thanks for the help everybody.

"Brian" <reply2me@thenewsgroup> wrote in message
news:...
> "Ace Fekay [MCT]" <> wrote
>> Sure, as long as it's a separate DHCP scope for the Guest network.
>
> It is.
>
> Thanks for the help everybody.

Then you should be fine. Keep in mind, any guests on the Guest network, if
they happen to be internal users, will not be able to access internal
resources unless they were to VPN in.

Ace