Problems with website access with a domain ending with .com

Ryan Laurie

I have a Windows 2003 Server that was setup before I got involved, at one
point they were hosting their own website. The issue that I have now is that
the domain is setup with a .com after the domain name instead of the .local,
so when I try to access the website, which is now being hosted by godaddy, I
can't get to it in the office. The site is setup on a web hosting server
that has a dynamic address, but for now I paid for a static ip for 2 months
because of other circumstances. The only way I have gotten it to work is
that I had to make an A record in the servers DNS pointing
to the static address. My issue is after the static number goes a way I will
lose access to the website in the office. I either have to find a way to
route the dns to connect to the dynamic website or there is a setting I'm
missing. Already cleared the DNS cache, removed the A record in hopes of
having the external DNS pickup my website but nothing seems to work other
than the A record in my office's DNS. Thanks Ryan.

Chris Dent

Hi Ryan,

I'm afraid that's the disadvantage of using public domain names for AD.

Your internal DNS server will claim authority for mydomain.com, as such it
will never forward an unresolved request for that domain elsewhere.

I guess you could potentially have a script watch the public record and
update the internal DNS server accordingly. It's about the only solution I
can think of if the public record is dynamic.

Chris

"Ryan Laurie" <> wrote in message
news:...
>I have a Windows 2003 Server that was setup before I got involved, at one
> point they were hosting their own website. The issue that I have now is
> that
> the domain is setup with a .com after the domain name instead of the
> .local,
> so when I try to access the website, which is now being hosted by godaddy,
> I
> can't get to it in the office. The site is setup on a web hosting server
> that has a dynamic address, but for now I paid for a static ip for 2
> months
> because of other circumstances. The only way I have gotten it to work is
> that I had to make an A record in the servers DNS pointing
>
> to the static address. My issue is after the static number goes a way I
> will
> lose access to the website in the office. I either have to find a way to
> route the dns to connect to the dynamic website or there is a setting I'm
> missing. Already cleared the DNS cache, removed the A record in hopes of
> having the external DNS pickup my website but nothing seems to work other
> than the A record in my office's DNS. Thanks Ryan.

Ryan Laurie

If you had to write a script what and how would you write and implement it?
I could also just pay the $2 a month to keep it static if you think that is
the easier and better choice. Thanks Ryan.

"Chris Dent" wrote:

>
> Hi Ryan,
>
> I'm afraid that's the disadvantage of using public domain names for AD.
>
> Your internal DNS server will claim authority for mydomain.com, as such it
> will never forward an unresolved request for that domain elsewhere.
>
> I guess you could potentially have a script watch the public record and
> update the internal DNS server accordingly. It's about the only solution I
> can think of if the public record is dynamic.
>
> Chris
>
> "Ryan Laurie" <> wrote in message
> news:...
> >I have a Windows 2003 Server that was setup before I got involved, at one
> > point they were hosting their own website. The issue that I have now is
> > that
> > the domain is setup with a .com after the domain name instead of the
> > .local,
> > so when I try to access the website, which is now being hosted by godaddy,
> > I
> > can't get to it in the office. The site is setup on a web hosting server
> > that has a dynamic address, but for now I paid for a static ip for 2
> > months
> > because of other circumstances. The only way I have gotten it to work is
> > that I had to make an A record in the servers DNS pointing
> >
> > to the static address. My issue is after the static number goes a way I
> > will
> > lose access to the website in the office. I either have to find a way to
> > route the dns to connect to the dynamic website or there is a setting I'm
> > missing. Already cleared the DNS cache, removed the A record in hopes of
> > having the external DNS pickup my website but nothing seems to work other
> > than the A record in my office's DNS. Thanks Ryan.
>
>
>

Chris Dent

Quite a few choices for that one, PowerShell and VbScript can both deal with
it easily enough.

It would run something like this (minor differences depending on language
used):

1. Query authoritative servers for mydomain.com for current IP for www
2. Query internal servers for mydomain.com for current IP for www
3. If values are different use WMI to modify the value on the internal
server

You would still have to deal with client caching after the change, not a
huge problem if the TTL for the record is very low (internally).

However, if the cost of keeping it static is trivial it would be better to
do that, saves everyone from potential breaks and keeps things nice and
simple (or as simple as possible).

Chris

"Ryan Laurie" <> wrote in message
news:...
> If you had to write a script what and how would you write and implement
> it?
> I could also just pay the $2 a month to keep it static if you think that
> is
> the easier and better choice. Thanks Ryan.
>
> "Chris Dent" wrote:
>
>>
>> Hi Ryan,
>>
>> I'm afraid that's the disadvantage of using public domain names for AD.
>>
>> Your internal DNS server will claim authority for mydomain.com, as such
>> it
>> will never forward an unresolved request for that domain elsewhere.
>>
>> I guess you could potentially have a script watch the public record and
>> update the internal DNS server accordingly. It's about the only solution
>> I
>> can think of if the public record is dynamic.
>>
>> Chris
>>
>> "Ryan Laurie" <> wrote in message
>> news:...
>> >I have a Windows 2003 Server that was setup before I got involved, at
>> >one
>> > point they were hosting their own website. The issue that I have now
>> > is
>> > that
>> > the domain is setup with a .com after the domain name instead of the
>> > .local,
>> > so when I try to access the website, which is now being hosted by
>> > godaddy,
>> > I
>> > can't get to it in the office. The site is setup on a web hosting
>> > server
>> > that has a dynamic address, but for now I paid for a static ip for 2
>> > months
>> > because of other circumstances. The only way I have gotten it to work
>> > is
>> > that I had to make an A record in the servers DNS pointing
>> >
>> > to the static address. My issue is after the static number goes a way
>> > I
>> > will
>> > lose access to the website in the office. I either have to find a way
>> > to
>> > route the dns to connect to the dynamic website or there is a setting
>> > I'm
>> > missing. Already cleared the DNS cache, removed the A record in hopes
>> > of
>> > having the external DNS pickup my website but nothing seems to work
>> > other
>> > than the A record in my office's DNS. Thanks Ryan.
>>
>>
>>

Phillip Windell

"Ryan Laurie" <> wrote in message
news:...
> because of other circumstances. The only way I have gotten it to work is
> that I had to make an A record in the servers DNS pointing
>
> to the static address. My issue is after the static number goes a way I
> will
> lose access to the website in the office.

The DNS A Record is the normal way to handle it. It is called
Split-DNS,...your DNS Server is the private side of the Split,...the
website's registar's DNS Server (or whoever is the authoritative DNS for the
public Domain) is the public half of the Split. Split-DNS is done both when
the AD Domain matches the Public Domain and again even when they don't
match, however the actual details of the Split-DNS configuration changes
slight between the two situations.

Pay the $2 dolloars a month and keep it static. A website with a dynamic
number is just asking for problems in the first place.

--
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.
-----------------------------------------------------