|
Home > Archive > Web Servers on Unix and Linux > May 2005 > nameservers and perls of buying cheap domain name
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
nameservers and perls of buying cheap domain name
|
|
| newsreader 2005-05-23, 8:47 pm |
| I have purchased a "cheapo" domain name (for the purpose of selling my home)
from a popular seach engine site, but the downfall is that unless I display
an ad, I have to show the redirect IP address. i.e www.mynew-domainname.com
points to my server IP and it is now displayed while users are surfing my
site.
My question is: Is there a way around this, e.g. by specifying the server
name in my httpd.conf and/or specifying a new DNS server that is running on
my server. I have some control over A record, C name, and primary and
secondary nameservers. Can I create links on my website to
www.mynew-domainname.com/somedir without it linking back to the homepage due
to the redirection limitation.
I am root user on my server, using comcast as ISP OS sol 8, and apache 1.39(I
believe).
Thanks
MikeD
| |
| Andrei Ivanov 2005-05-23, 8:47 pm |
| newsreader <cc0101172@minix.midltn01.nj.comcast.net> wrote:
> I have purchased a "cheapo" domain name (for the purpose of selling my home)
> from a popular seach engine site, but the downfall is that unless I display
> an ad, I have to show the redirect IP address. i.e www.mynew-domainname.com
> points to my server IP and it is now displayed while users are surfing my
> site.
Couldn't you just tell your domain name? Otherwise it's not
really clear what you've got.
--
andrei
| |
| Mike Dundas 2005-05-24, 5:57 pm |
| I chose not to publish my domain name as I am monitering hits to my site to
see how much interest my house sale is generating.
lets just say I bought www.mydname.com and yahoo forwards this to
http://69.7.239.163/housesale
yahoo gives me control over the following:
A Name mydname.com
A Name www.mydname.com
CNAME *.mydname.com
CNAME mail.mydname.com
I can add records and I am allowed to specify two nameservers, currently
defaulting to yns1.yahoo.com and yns2.yahoo.com
For example, when users click www.mydname.com yahoo forwards them to, lets
say, http://69.7.239.163/housesale. They have the IP address in the url
toolbar of their browser. I would like to stop this. I wondered if
modifying my httpd.conf to specify domainname as www.mydname.com and maybe
some virtual host trickery in addition to setting up a dns server on my
solaris box 69.7.239.163 would be the way to go. Is this possible? Can I
avoid showing my IP address, it just doesn't look professional. Yahoo wants
me to display their ad to do this. I thought there must be some way around
this.
I hope this clarifies my problem.
Thanks
Mike D
"Andrei Ivanov" <iva@racoon.riga.lv> wrote in message
news:3fffheF77sqrU1@individual.net...
> newsreader <cc0101172@minix.midltn01.nj.comcast.net> wrote:
>
> Couldn't you just tell your domain name? Otherwise it's not
> really clear what you've got.
>
> --
> andrei
| |
|
| On Mon, 23 May 2005 20:01:58 -0500,
newsreader <cc0101172@minix.midltn01.nj.comcast.net> posted:
> I have purchased a "cheapo" domain name (for the purpose of selling my home)
> from a popular seach engine site, but the downfall is that unless I display
> an ad, I have to show the redirect IP address. i.e www.mynew-domainname.com
> points to my server IP and it is now displayed while users are surfing my
> site.
For something as transient as selling your own house, why not spend a tiny
bit extra for a better service, since you won't have to be shelling out for
it for years and years? There are a multitude of very cheap services that
will do what you want. We're only talking a matter of a few dollars, to do
it right, not hundreds.
> My question is: Is there a way around this, e.g. by specifying the server
> name in my httpd.conf and/or specifying a new DNS server that is running on
> my server.
It isn't going to help you unless your DNS record points to the IP in use,
which it sounds like it isn't, because you're using a redirect.
Messing with frames can hide your IP from casual observers, but do you more
harm than good in various other ways (search for "frames are evil" to save
me typing them all in here).
--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.
This message was sent without a virus, please delete some files yourself.
| |
| Andrei Ivanov 2005-05-24, 8:47 pm |
| Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
> lets just say I bought www.mydname.com and yahoo forwards this to
> http://69.7.239.163/housesale
>
> yahoo gives me control over the following:
> A Name mydname.com
> A Name www.mydname.com
Both A-records, for "mydname.com" and "www.mydname.com",
should point to the same ip address, 69.7.239.163.
> CNAME *.mydname.com
Perhaps you don't need this (above).
> modifying my httpd.conf to specify domainname as www.mydname.com and maybe
> some virtual host trickery in addition to setting up a dns server on my
> solaris box 69.7.239.163 would be the way to go. Is this possible?
If you're using Apache, then in its config file you'll have something
like this
<VirtualHost 69.7.239.163:80>
ServerName www.mydname.com
ServerAlias mydname.com
...
</VirtualHost>
As a result, whenever web user will enter either http://mydname.com/,
or http://www.mydname.com/, he'll be directed to Apache daemon running
at 69.7.239.163, and this daemon will have enough information to
serve the same content for both 2nd and 3rd level domain.
--
andrei
| |
| newsreader 2005-05-25, 8:47 pm |
| Tim <tim@mail.localhost.invalid> wrote:
> On Mon, 23 May 2005 20:01:58 -0500,
> newsreader <cc0101172@minix.midltn01.nj.comcast.net> posted:
>
>
> For something as transient as selling your own house, why not spend a tiny
> bit extra for a better service, since you won't have to be shelling out for
> it for years and years? There are a multitude of very cheap services that
> will do what you want. We're only talking a matter of a few dollars, to do
> it right, not hundreds.
>
>
> It isn't going to help you unless your DNS record points to the IP in use,
> which it sounds like it isn't, because you're using a redirect.
>
> Messing with frames can hide your IP from casual observers, but do you more
> harm than good in various other ways (search for "frames are evil" to save
> me typing them all in here).
>
I believe it is pointing at the correct IP address. the forward redirects the
server requests to my comcast IP address. Andre has suggested using virtual
hosts. I have done this, but by entering www.mydname.com in the address bar of
my browser (or mydname.com) links me to my server, but the browser displays the
IP address.
I have changed ServerName directive to my domainname and have added
NameVirtualHost ip:port
and virtual hosts has IP address and Servername included. I am not sure if this
is due to yahoo redirect or some apache configs.
thanks,
Mike D
| |
|
| newsreader <cc0101172@minix.midltn01.nj.comcast.net> posted:
Tim <tim@mail.localhost.invalid> wrote:
[vbcol=seagreen]
newsreader <cc0101172@minix.midltn01.nj.comcast.net> posted:
[vbcol=seagreen]
> I believe it is pointing at the correct IP address. the forward redirects the
> server requests to my comcast IP address.
If the domain name pointed to your IP, then there'd be no need to mess with
anything, it'd just work. Therefore, it's a safe bet that it doesn't. But
we can't tell, because you've not provided any real details.
This sounds very much like the domain name points to someone else's IP.
The server at that address has a page that direct them to your IP.
Trying to mask your server with their domain name isn't going to work,
because it's going to send browsers right back to their IP (when the
browser resolves the domain name).
If you're unwilling to tell us the domain name and IPs involved, and I
can't see why (seeing as you're trying to sell something, that will expose
you to the public), you can resolve this for yourself.
On *ix systems you can use the dig command on your domain name to find out
what IP it refers to. You can do the same sort of thing on Windows, but I
don't know the command (pinging the domain might expose the IP in the
responses). If it's different than the IP address you're trying to serve
webpages from then you're going to have to abandon messing with your
webserver to resolve the issue, the problems is elsewhere.
--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.
This message was sent without a virus, please delete some files yourself.
| |
| Mike Dundas 2005-05-26, 5:54 pm |
|
"Tim" <tim@mail.localhost.invalid> wrote in message
news:1n76iq9uny8ej$.1isye3nidomny$.dlg@40tude.net...
> newsreader <cc0101172@minix.midltn01.nj.comcast.net> posted:
>
>
>
> Tim <tim@mail.localhost.invalid> wrote:
>
>
> newsreader <cc0101172@minix.midltn01.nj.comcast.net> posted:
>
>
> If the domain name pointed to your IP, then there'd be no need to mess
> with
> anything, it'd just work. Therefore, it's a safe bet that it doesn't.
> But
> we can't tell, because you've not provided any real details.
>
> This sounds very much like the domain name points to someone else's IP.
> The server at that address has a page that direct them to your IP.
> Trying to mask your server with their domain name isn't going to work,
> because it's going to send browsers right back to their IP (when the
> browser resolves the domain name).
>
> If you're unwilling to tell us the domain name and IPs involved, and I
> can't see why (seeing as you're trying to sell something, that will expose
> you to the public), you can resolve this for yourself.
>
> On *ix systems you can use the dig command on your domain name to find out
> what IP it refers to. You can do the same sort of thing on Windows, but I
> don't know the command (pinging the domain might expose the IP in the
> responses). If it's different than the IP address you're trying to serve
> webpages from then you're going to have to abandon messing with your
> webserver to resolve the issue, the problems is elsewhere.
>
> --
> If you insist on e-mailing me, use the reply-to address (it's real but
> temporary). But please reply to the group, like you're supposed to.
>
> This message was sent without a virus, please delete some files yourself.
Tim,
please excuse my obscurity. House is now for sale by realtor exclusivly (I
can no longer advertise anyway). The reason I am so paranoid is I assume
that there that there are people who would love to take pride in my
server. Even with only ssh, www, and ftp on my box I get enough attempts in
my /var/adm/logs to see that without advertising its wherabouts on the
newsgroups, attemped hacks are a reality. I will install bind and run the
command and see what comes back.
thanks again for your input, sorry again for my obscurity.
I appreciate you help!
Mike
| |
| newsreader 2005-05-26, 5:54 pm |
| Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
>
> "Tim" <tim@mail.localhost.invalid> wrote in message
> news:1n76iq9uny8ej$.1isye3nidomny$.dlg@40tude.net...
>
> Tim,
> please excuse my obscurity. House is now for sale by realtor exclusivly (I
> can no longer advertise anyway). The reason I am so paranoid is I assume
> that there that there are people who would love to take pride in my
> server. Even with only ssh, www, and ftp on my box I get enough attempts in
> my /var/adm/logs to see that without advertising its wherabouts on the
> newsgroups, attemped hacks are a reality. I will install bind and run the
> command and see what comes back.
>
> thanks again for your input, sorry again for my obscurity.
>
> I appreciate you help!
>
> Mike
>
>
here is the output of dig. I ran command 4 times. let me know if you need
it run with different params.
# dig www.mydname.com
; <<>> DiG 8.3 <<>> www.mydname.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; www.mydname.com, type = A, class = IN
;; ANSWER SECTION:
www.mydname.com. 20S IN CNAME premium5.geo.yahoo.akadns.net.
premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.46
premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.47
premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.44
premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.45
;; Total query time: 9 msec
;; FROM: saltire to SERVER: default -- 10.0.64.144
;; WHEN: Thu May 26 18:52:02 2005
;; MSG SIZE sent: 34 rcvd: 141
# dig mydname.com
; <<>> DiG 8.3 <<>> mydname.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; mydname.com, type = A, class = IN
;; ANSWER SECTION:
mydname.com. 1m1s IN A 68.142.234.45
mydname.com. 1m1s IN A 68.142.234.46
mydname.com. 1m1s IN A 68.142.234.47
mydname.com. 1m1s IN A 68.142.234.44
;; Total query time: 9 msec
;; FROM: saltire to SERVER: default -- 10.0.64.144
;; WHEN: Thu May 26 18:52:20 2005
;; MSG SIZE sent: 30 rcvd: 94
#
# dig mydname.com ANY
; <<>> DiG 8.3 <<>> mydname.com ANY
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 4, ADDITIONAL: 0
;; QUERY SECTION:
;; mydname.com, type = ANY, class = IN
;; ANSWER SECTION:
mydname.com. 32S IN A 68.142.234.44
mydname.com. 32S IN A 68.142.234.45
mydname.com. 32S IN A 68.142.234.46
mydname.com. 32S IN A 68.142.234.47
mydname.com. 23h50m32s IN NS yns1.yahoo.com.
mydname.com. 23h50m32s IN NS yns2.yahoo.com.
mydname.com. 23h50m32s IN NS ns8.san.yahoo.com.
mydname.com. 23h50m32s IN NS ns9.san.yahoo.com.
;; AUTHORITY SECTION:
mydname.com. 23h50m32s IN NS yns1.yahoo.com.
mydname.com. 23h50m32s IN NS yns2.yahoo.com.
mydname.com. 23h50m32s IN NS ns8.san.yahoo.com.
mydname.com. 23h50m32s IN NS ns9.san.yahoo.com.
;; Total query time: 14 msec
;; FROM: saltire to SERVER: default -- 10.0.64.144
;; WHEN: Thu May 26 18:52:50 2005
;; MSG SIZE sent: 30 rcvd: 234
# dig www.mydname.com ANY
; <<>> DiG 8.3 <<>> www.mydname.com ANY
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 4
;; QUERY SECTION:
;; www.mydname.com, type = ANY, class = IN
;; ANSWER SECTION:
www.mydname.com. 10M IN CNAME premium5.geo.yahoo.akadns.net.
;; ADDITIONAL SECTION:
premium5.geo.yahoo.akadns.net. 5M IN A 68.142.234.47
premium5.geo.yahoo.akadns.net. 5M IN A 68.142.234.44
premium5.geo.yahoo.akadns.net. 5M IN A 68.142.234.45
premium5.geo.yahoo.akadns.net. 5M IN A 68.142.234.46
;; Total query time: 149 msec
;; FROM: saltire to SERVER: default -- 10.0.64.144
;; WHEN: Thu May 26 18:53:23 2005
;; MSG SIZE sent: 34 rcvd: 141
Thanks
Mike D
| |
| Andrei Ivanov 2005-05-27, 5:50 pm |
| newsreader <cc0101172@minix.midltn01.nj.comcast.net> wrote:
> www.mydname.com. 20S IN CNAME premium5.geo.yahoo.akadns.net.
> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.46
> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.47
> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.44
> premium5.geo.yahoo.akadns.net. 1m16s IN A 68.142.234.45
Did you see my posting on 5/24/2005?
If so, then what part of it didn't you understand?
--
andrei
| |
| Mike Dundas 2005-05-27, 5:50 pm |
| "Andrei Ivanov" <iva@racoon.riga.lv> wrote in message
news:3fp8laF8vsmnU1@individual.net...
> newsreader <cc0101172@minix.midltn01.nj.comcast.net> wrote:
>
> Did you see my posting on 5/24/2005?
> If so, then what part of it didn't you understand?
>
> --
> andrei
Andrei,
I saw the post and tried adding the following to section 3 of the httpd.conf
NameVirtualHost <69.7.239.163:80>
<VirtualHost 69.7.239.163>
ServerName www.mydname.com
ServerAlias mydname.com
#ServerAlias www.mydname.com
# DocumentRoot /users/4sale/
</VirtualHost>
I then tried switching ServerName to mydname.com and alias to
www.mydname.com but this
didn't work either. I added 69.7.239.163 www.mydname.com to /etc/hosts and
also adding
www.mydname.com to ServerName in section 2 of httpd.conf I added IP address
entries to
Listen and BindAddress in conf file, but typing www.mydname.com/anypath to a
browser address
bar redirects all requests back to main IP address 69.7.239.163 as specified
by yahoo redirect.
For a while I had it working when dropping off www but I have tried so many
permutations I have forgotten which way I had it configured. I will have to
look in the O'Reily DNS
book I have at work.
In answer to your question, I wasn't familiar with terms "2nd and 3rd level
domain". Please excuse my
ignorance, this is a work in progress and something I haven't tackled
before.
Thanks for your help
MikeD.
| |
| Andrei Ivanov 2005-05-27, 5:50 pm |
| Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
>
> I then tried switching ServerName to mydname.com and alias to
> www.mydname.com but this didn't work either.
You've mentioned that you have control over your DNS records.
And I suggested that "both A-records, for "mydname.com" and
"www.mydname.com", should point to the same ip address,
69.7.239.163".
Right now the "mydname.com" domain name resolves to four
IP addresses. The "www.mydname.com" domain name also points
to the same IPs (premium5.geo.yahoo.akadns.net). Instead, both
should point to IP address of your own web server, 69.7.239.163.
Dig's output should report something like this:
mydname.com. 30m IN A 69.7.239.163
www.mydname.com. 30m IN A 69.7.239.163
Or this:
mydname.com. 30m IN A 69.7.239.163
www.mydname.com. 30m IN CNAME mydname.com.
Can you do that?
--
andrei
| |
| newsreader 2005-05-27, 8:47 pm |
| Andrei Ivanov <iva@racoon.riga.lv> wrote:
> Mike Dundas <mdundas@nospamthanks.comcast.net> wrote:
>
> You've mentioned that you have control over your DNS records.
> And I suggested that "both A-records, for "mydname.com" and
> "www.mydname.com", should point to the same ip address,
> 69.7.239.163".
>
> Right now the "mydname.com" domain name resolves to four
> IP addresses. The "www.mydname.com" domain name also points
> to the same IPs (premium5.geo.yahoo.akadns.net). Instead, both
> should point to IP address of your own web server, 69.7.239.163.
>
> Dig's output should report something like this:
>
> mydname.com. 30m IN A 69.7.239.163
> www.mydname.com. 30m IN A 69.7.239.163
>
> Or this:
>
> mydname.com. 30m IN A 69.7.239.163
> www.mydname.com. 30m IN CNAME mydname.com.
>
> Can you do that?
>
Andrei
I changed the A Record for www.mydname.com and mydname to point to
my IP but then yahoo somehow links the dominnames to a default homepage
which is basically a template on yahoo with rigid structure. I really dont
have much control over it and cannot embed html in the template.
If I set the "domain forward" to my ipaddress it goes to my site. As I
said I had it working for mydname.com (for a while at least) but adding
www to the domainname just sends me to the IP address and shows doc root.
should I have to add entries to Listen and BindAddress etc or just the
Virtual hosts directives?
I do have control over the Nameservers. Are these the authoritative servers?
If I were to set up DNS or Bind on my server is this an option, or is this a
huge task!
Thanks again,
Mike D
| |
| David Efflandt 2005-05-28, 7:47 am |
| On Fri, 27 May 2005, newsreader <cc0101172@minix.midltn01.nj.comcast.net>
wrote:
> Andrei Ivanov <iva@racoon.riga.lv> wrote:
> Andrei
>
> I changed the A Record for www.mydname.com and mydname to point to
> my IP but then yahoo somehow links the dominnames to a default homepage
> which is basically a template on yahoo with rigid structure. I really dont
> have much control over it and cannot embed html in the template.
>
> If I set the "domain forward" to my ipaddress it goes to my site. As I
> said I had it working for mydname.com (for a while at least) but adding
> www to the domainname just sends me to the IP address and shows doc root.
>
> should I have to add entries to Listen and BindAddress etc or just the
> Virtual hosts directives?
>
> I do have control over the Nameservers. Are these the authoritative servers?
> If I were to set up DNS or Bind on my server is this an option, or is this a
> huge task!
What you fail to grasp is that you are using a redirection or forwarding
service, so they determine what shows in the first part of the URL bar.
Nothing you do in apache is going to change that until you do away with
the redirection or forwarding altogether, and have names resolve in
"public" DNS directly to the public IP of your server (your comcast
connection?).
Until you can get host or nslookup or dig to resolve your names to the
public IP of "your" server, any attempt to reconfigure your apache to show
your domain name will be futile. For now, the names apparently resolve to
the redirection or forwarder service that is not under your control.
| |
| Mike Dundas 2005-05-28, 8:46 pm |
|
"David Efflandt" <efflandt@xnet.com> wrote in message
news:slrnd9gih7.24f.efflandt@typhoon.xnet.com...
> service, so they determine what shows in the first part of the URL bar.
> Nothing you do in apache is going to change that until you do away with
> the redirection or forwarding altogether, and have names resolve in
> "public" DNS directly to the public IP of your server (your comcast
> connection?).
>
> Until you can get host or nslookup or dig to resolve your names to the
> public IP of "your" server, any attempt to reconfigure your apache to show
> your domain name will be futile. For now, the names apparently resolve to
> the redirection or forwarder service that is not under your control.
David,
is it then possible to have the address resolved by my own dns server. Or,
as you point out, (Re: fail to grasp), this also has nothing to do with it
and even
using my own nameservers will not change this!
Thank you,
Mike D
| |
|
| On Sat, 28 May 2005 19:39:06 -0400,
"Mike Dundas" <mdundas@Nospamthanks.comcast.net> posted:
> is it then possible to have the address resolved by my own dns server. Or,
> as you point out, (Re: fail to grasp), this also has nothing to do with it
> and even using my own nameservers will not change this!
You need to change a few things.
You need a webserving host that you can properly control. One that you can
set the domain name that it responds to. That's a webserver configuration
and a DNS configuration issue.
You need your domain name registered with a service that allows you to set
the domain name to point to the IP that you want, directly. No redirection
services.
Let's say you register the domain "example.com", and you also pay for
website hosting from some webhost that serves from the numerical IP address
of 192.0.34.166.
You configure your DNS records to point example.com to 192.0.34.166, and
vice versa, using 192.0.34.43 and 193.0.0.236 as the authoritative name
server for your domain. (Do a dig on that domain name to see.) You'd
probably also configure www.example.com to point to the same 192.0.34.166
numerical IP address.
Alternatively, you might use the webhost's DNS servers as your
authoritative DNS server. You don't have to. You can manage your DNS
anywhere that you care to, so long as the other host that's serving your
files doesn't enforce some annoying restrictions on you.
Then comes the configuration for the webserver. In some cases there
mightn't need to be any customisation, it might simply respond to requests
it receives as they come. But, these days, most low budget hosts use one
webserver to serve out multiple websites (virtual hosting). They need each
site to be configured for the domain name(s) that they respond to.
But if you use some cheap redirecting service, you can throw all of that
out the window. The DNS data points to the redirecting serving in the
middle. And the point I made earlier still stands, there's not that much
price difference between this silly way of doing it, and the proper way of
doing it. You've just to got to look around a bit to find the services
that you need.
As a general warning, be careful about paying to register a domain name
through the same company that will host your webpages. You might find it
difficult to separate the two, if you need to (some contract you into a
corner, others are just plain annoying to try and deal with). You may also
find that they own the domain name (e.g. example.com), and you're just
paying for a sub-domain (e.g. myspace.example.com).
--
If you insist on e-mailing me, use the reply-to address (it's real but
temporary). But please reply to the group, like you're supposed to.
This message was sent without a virus, please delete some files yourself.
| |
| David Efflandt 2005-05-30, 8:47 pm |
| On Sat, 28 May 2005, Mike Dundas <mdundas@Nospamthanks.comcast.net> wrote:
>
> "David Efflandt" <efflandt@xnet.com> wrote in message
> news:slrnd9gih7.24f.efflandt@typhoon.xnet.com...
>
>
> David,
> is it then possible to have the address resolved by my own dns server. Or,
> as you point out, (Re: fail to grasp), this also has nothing to do with it
> and even using my own nameservers will not change this!
Typically for your own nameserver to do public DNS, it would need to be a
static IP (DHCP that rarely changes may not be good enough) and would be
need to be set as a nameserver for your domain with your domain registrar.
Most require at least 2 nameservers. That also assumes that you can
properly configure bind (named).
If you have a dynamic IP or are unsure of your abilites to configure a
nameserver, there are other services that can do that. I may have
mentioned that I use no-ip.com, but you can find others with a web search
for 'dns hosting'. Just remember that you need to tell your registrar the
nameservers for your domain before they will work for the public. And if
previous expire time was too long, it may take awhile (days to a week)
before it will expire from present DNS caches. Dynamic DNS services may
expire in 1 to 5 minutes, so they do not remain in cache very long.
|
|
|
|
|