domain won't resolve with www prefix

[Trialsman]

Hi, folks. I have just spent four hours on my RH7.1 DNS server and it finally resolves my domain name for the first time ever. Sort of.

My domain name is discovermountainbiking.net and that works, try it. BUT! I don't understand this and nothing I have done fixed it,

http://www.discovermountainbiking.net

does NOT resolve.

I need help!

Thanks much.

 

[ifincham]

Hi,

Well, your name servers point to 4.36.122.184 & 4.36.122.184 but I don't have the tools right now to query them very well. 'discovermountainbiking.net' resolves to 192.168.123.201 however which is an internal address that is not reachable from the public internet - its in the 'private' class C range 192.168.0.0 - 192.168.255.255 .
In other words, no-one can browse that address from outside.

You need to set it to your internet interface IP address (4.36.122.184) to start with! I can connect to your site from here with -->

http://4.36.122.184

however.

Can't check much more for now....

Regards

 

[Trialsman]

Okay. Thanks for the response!

I dug around and found some good BIND and Apache tips. I made some changes and hurray! I can now resolve

http://www.discovermountainbiking.net!!

The way I had the site coming up originally was simply the fact that it was default. Any request to my IP gave that page. A tip from Redhat says that is wrong. So I put the default back to the Redhat default, the Apache successful load page.

Now I can't resolve discovermountainbiking.net without the

http://www...

Geesh.

Thanks for your help. I am making progress!

 

[marsd]

Hint: cname or another A record.
see ya.
MMD

 

[ifincham]

Hi,









Maybe you're working on it right now but I can't resolve

http://www.discovermountainbiking.net

from here. You first dns address gives 'SERVFAIL' errors and the other one (4.36.122.185) doesn't respond at all.









; <<>> DiG 9.1.3 <<>> @4.36.122.184 discovermountainbiking.net soa




;; global options: printcmd




;; Got answer:




;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18649




;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0









;; QUESTION SECTION:




;discovermountainbiking.net. IN SOA









;; Query time: 295 msec




;; SERVER: 4.36.122.184#53(4.36.122.184)




;; WHEN: Sat Aug 18 16:37:50 2001




;; MSG SIZE rcvd: 44









Also I only get the apache server default page if I do

http://4.36.122.184/

or even

http://www.discovermountainbiking.net

(having first put it in my /etc/hosts file to make sure I can use the canonical name) - i.e. in case you are using apache virtual hosts, etc. and it needs the 'www' name.
I can connect to

http://www.discovermountainbiking.com

though - is that your 'old' site ?

Rgds

 

[optimised]

Hi,
I'm having the same difficulties. I have been trying to get this working for a week now. The only way can get my domain is by using my nameserver ip in browser.
I used myhostman.com to register my nameservers and set up a beta site. My servers are ns1.myhostman.com and ns2.myhostman.com 206.107.69.66 and 206.107.69.67
I am able to ping my ip and ns1 names. But dig@ 206.107.69.66 results in server fail as well.
Seems that trailsman and I are missing a small detail somewhere. I am using virtual hosting and can't figure out whats missing. These are my config files.

//httpd.conf

NameVirtualHost 206.107.69.66

<VirtualHost 206.107.69.66>
ServerName

http://www.myhostman.com

DocumentRoot /myhostman/www/
</VirtualHost>

//resolv.conf
search myhostman.com
nameserver 205.162.9.254 (my isp' nameserver)
nameserver 206.107.69.66 (my ns1 ip)

//zone file
$TTL 86400
@ IN SOA ns1.myhostman.com. hostmaster.myhostman.com. (
20010814; Serial
12H ; Refresh
1H ; Retry
2W ; Expire
1D ) ; Minimum
IN NS ns1.myhostman.com.
IN NS ns2.myhostman.com.
www IN A 205.162.9.218
ftp IN A 205.162.9.218
www IN A 205.162.9.219
mail IN A 205.162.9.219
IN MX 5 mail.myhostman.com.

Good luck trailsman maybe eventually we will get them working.

 

[optimised]

btw- If I run dig on ns1 (eg)dig @206.107.69.66
it returns

http://www.myhostman.com

IN SOA ns1.myhostman.com. hostmaster.myhostman.com. (

So it seems to resolve fine here using 'server 206.107.69.66

 

[marsd]

These problems are usually symptomatic of reverse zone problems.

make sure that your records look something like this:
$TTL 1D
zone file name (@) IN SOA domain.name. contact.me. (

serialval
refreshval
retryval
expiryval
minttlval )

IN NS domain.name.
(faux ipaddress is 192.168.1.45)
45 IN PTR domain.name.
#webserver
46 IN PTR

http://www.domain.name.

47 IN PTR mx.domain.name.

Use the host comnmand to tshoot any further dns trouble:
It is an easy to use and versatile tool capable of recursive lookups and axfr's.

Good Luck.

 

[ifincham]

Hi - optimised











Your one's a bit different I think.. I get timeouts trying to contact your dns server :











; <<>> DiG 9.1.3 <<>> @206.107.69.66 localhost





;; global options: printcmd





;; connection timed out; no servers could be reached











And '/usr/sbin/traceroute 206.107.69.66 -p 53' gives this (end part) :

















15 sl-bb22-pen-10-0.sprintlink.net (144.232.9.70) 102.412 ms 101.059 ms 105.062 ms





16 144.232.5.86 (144.232.5.86) 103.587 ms 101.217 ms 96.689 ms





17 sl-broadcom-2-0.sprintlink.net (160.81.65.26) 106.537 ms 112.973 ms 105.009 ms





18 * * *





19 172.17.2.233 (172.17.2.233) 127.760 ms 129.729 ms 126.283 ms





20 172.17.2.246 (172.17.2.246) 125.531 ms 124.564 ms 130.313 ms





21 172.17.2.249 (172.17.2.249) 127.903 ms 125.069 ms 129.691 ms





22 172.17.2.246 (172.17.2.246) 137.148 ms 127.648 ms 126.416 ms





23 * * *





24 * * *





25 206.107.69.66 (206.107.69.66) 144.017 ms 141.110 ms 140.742 ms











Seems to take a (relatively) long time between hop 17 and 25 - This is presumably at your ISP... Also some NMAP scans still show port 53 as 'filtered' rather than 'open'.
If you're firewalling now are you letting port 53 through for both tcp and udp protocols ?










I know this isn't very helpful but it does still indicate that there is (also ?) a problem accessing your dns server in the first place from the internet whereas Trialsman's server responds but does so with errors.











Regards

 

[Trialsman]

Thanks ifincham and marsd for your responses. It turns out that I had totally ruined all my zone records by adding a letter to the serial number to help me keep track of changes. Not much was working this morning.

Dig told me I was no longer authoritative for any of my zones, and the logs told me my mistake. All that is fixed now.

Here is the really confusing part. I have two domains up now, discovermountainbiking.net and absolutelybrilliant.net. The zone files for these two names are identical. The httpd.conf virtualhost listings are identical with the exception of a different class C IP.

All zone files refer to them in exactly the way they should. BUT!

http://www.discovermountainbiking.net

resolves correctly to my server and discovermountainbiking.net resolves incorrectly to the apache default page.

http://www.absolutelybrilliant.net

resolves to a hosting service but absolutelybrilliant.net resolves correctly to my server.

It's weird. I really appreciate the help. I am making progress at least. And I see others have similar problems. I'll write a FAQ about all this when I work it all out.

Thanks again.

 

[optimised]

Hi,
Just wondering If I'm only using one ip address for virtualhosting and had two domains how would you create the reverse zone file to accomadate both domains? I thought I would not need reverse zones because I'm only using my one ip and namevirtualhost 206.107.69.66? Not sure how to create the reverse zone file/files with the same name. 69.107.206

thanks

 

[ifincham]

Hi - Trialsman,

This is what I get for

http://www.discovermountainbiking.net

(using my isp's dns)...

; <<>> DiG 9.1.3 <<>>

http://www.discovermountainbiking.net

;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58120
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;

http://www.discovermountainbiking.net.

IN A

;; ANSWER SECTION:

http://www.discovermountainbiking.net.

86400 IN A 4.36.122.184

;; AUTHORITY SECTION:

http://www.discovermountainbiking.net.

86400 IN NS ns1.discovermountainbiking.net.

;; Query time: 4094 msec
;; SERVER: 213.1.119.100#53(213.1.119.100)
;; WHEN: Sat Aug 18 21:51:00 2001
;; MSG SIZE rcvd: 82

And this is what I get for

http://www.absolutelybrilliant.net....

; <<>> DiG 9.1.3 <<>>

http://www.absolutelybrilliant.net

;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39250
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;

http://www.absolutelybrilliant.net.

IN A

;; ANSWER SECTION:

http://www.absolutelybrilliant.net.

86225 IN A 4.36.122.184

;; AUTHORITY SECTION:

http://www.absolutelybrilliant.net.

86225 IN NS ns1.discovermountainbiking.net.

;; ADDITIONAL SECTION:
ns1.discovermountainbiking.net. 172625 IN A 4.36.122.184

;; Query time: 53 msec
;; SERVER: 213.1.119.100#53(213.1.119.100)
;; WHEN: Sat Aug 18 21:53:03 2001
;; MSG SIZE rcvd: 118


So, you can see that they both return the same ipaddress - however, they also both still give me your apache default install page so there is still a problem with your virtual hosting...

Regardz

 

[Trialsman]

ifincham, those are the responses I get from DIG from my ISPs DNS as well. But I do not get the same pages as you... Perhaps you can give me your ISPs DNS server IPs and I can reset my router with those, so I can try surfing from outside my ISP...

What do you say?

 

[ifincham]

Hi,

Not sure quite what you mean but anyway - My ISP's DNS servers are at :

213.1.119.99 & 213.1.119.100

Rgds

 

[Trialsman]

To answer my own question, I set my router to use the DNS of web2010. I get the same responses as when I use my ISPs DNS.

(I am abbreviating discovermountainbiking as dmtb and absolutelybrilliant as abril)

http://www.dmtb.net

- my server, correct page
dmtb.net - my server, apache page

http://www.abril.net

- some other companies page
abril.net - my server, correct page

Why do you get something different?

 

[Trialsman]

I am not sure what I mean. All I know is, I don't get the same pages as you do when I type in the same things in my browser...

Could we swap e-mail addresses or ICQ numbers to help us communicate? I will post whatever solutions we come up with on here so others will know, if many are following this thread.

My address is dan@discovermountainbiking.com.

 

[ifincham]

Hi,

http://www.dmtb.net

from my ISP's dns :

; <<>> DiG 9.1.3 <<>>

http://www.dmtb.net

;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 65227
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;

http://www.dmtb.net.

IN A

;; AUTHORITY SECTION:
net. 10751 IN SOA A.GTLD-SERVERS.net. hostmaster.nsiregistry.net. 2001081800 1800 900 604800 86400

;; Query time: 66 msec
;; SERVER: 213.1.119.100#53(213.1.119.100)
;; WHEN: Sat Aug 18 22:38:19 2001
;; MSG SIZE rcvd: 104

same from your dns...

; <<>> DiG 9.1.3 <<>> @4.36.122.184

http://www.dmtb.net

;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35976
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;

http://www.dmtb.net.

IN A

;; AUTHORITY SECTION:
net. 10787 IN SOA A.GTLD-SERVERS.net. hostmaster.nsiregistry.net. 2001081701 1800 900 604800 86400

;; Query time: 205 msec
;; SERVER: 4.36.122.184#53(4.36.122.184)
;; WHEN: Sat Aug 18 22:39:31 2001
;; MSG SIZE rcvd: 104

Then

http://www.abril.net

from my ISP'd dns:

; <<>> DiG 9.1.3 <<>>

http://www.abril.net

;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42962
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;

http://www.abril.net.

IN A

;; ANSWER SECTION:

http://www.abril.net.

86076 IN A 64.75.34.136

;; AUTHORITY SECTION:
abril.net. 172476 IN NS NS1.MYDOMAIN.COM.
abril.net. 172476 IN NS NS2.MYDOMAIN.COM.
abril.net. 172476 IN NS NS3.MYDOMAIN.COM.
abril.net. 172476 IN NS NS4.MYDOMAIN.COM.

;; ADDITIONAL SECTION:
NS1.MYDOMAIN.COM. 82824 IN A 216.34.13.236
NS2.MYDOMAIN.COM. 49149 IN A 64.75.34.132
NS3.MYDOMAIN.COM. 39285 IN A 64.75.34.140
NS4.MYDOMAIN.COM. 46725 IN A 64.75.34.134

;; Query time: 49 msec
;; SERVER: 213.1.119.100#53(213.1.119.100)
;; WHEN: Sat Aug 18 22:42:01 2001
;; MSG SIZE rcvd: 195

and from yours...

; <<>> DiG 9.1.3 <<>> @4.36.122.184

http://www.abril.net

;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24141
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;

http://www.abril.net.

IN A

;; ANSWER SECTION:

http://www.abril.net.

86400 IN A 64.75.34.136

;; AUTHORITY SECTION:
abril.net. 259200 IN NS ns1.mydomain.com.
abril.net. 259200 IN NS ns2.mydomain.com.
abril.net. 259200 IN NS ns3.mydomain.com.
abril.net. 259200 IN NS ns4.mydomain.com.

;; ADDITIONAL SECTION:
ns1.mydomain.com. 172800 IN A 216.34.13.236
ns2.mydomain.com. 172800 IN A 64.75.34.132
ns3.mydomain.com. 172800 IN A 64.75.34.140
ns4.mydomain.com. 172800 IN A 64.75.34.134

;; Query time: 1579 msec
;; SERVER: 4.36.122.184#53(4.36.122.184)
;; WHEN: Sat Aug 18 22:42:56 2001
;; MSG SIZE rcvd: 195

Your dns .. just abril.net ..

; <<>> DiG 9.1.3 <<>> @4.36.122.184 abril.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20124
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;abril.net. IN A

;; ANSWER SECTION:
abril.net. 86400 IN A 64.75.34.136

;; AUTHORITY SECTION:
abril.net. 259200 IN NS ns4.mydomain.com.
abril.net. 259200 IN NS ns1.mydomain.com.
abril.net. 259200 IN NS ns2.mydomain.com.
abril.net. 259200 IN NS ns3.mydomain.com.

;; ADDITIONAL SECTION:
ns1.mydomain.com. 172693 IN A 216.34.13.236
ns2.mydomain.com. 172693 IN A 64.75.34.132
ns3.mydomain.com. 172693 IN A 64.75.34.140
ns4.mydomain.com. 172693 IN A 64.75.34.134

;; Query time: 365 msec
;; SERVER: 4.36.122.184#53(4.36.122.184)
;; WHEN: Sat Aug 18 22:44:43 2001
;; MSG SIZE rcvd: 191


Seems to me you are getting different answers in some cases..

Rgds

 

[Trialsman]

I'm sorry your went through all that work. You must not have seen my note about using abbreviations, so I didn't have to type absolutelybrilliant.net and discovermountainbiking.net all those times.

dmbt and abril are legitimately owned by someone else, as you found out...

I meant:

http://www.discovermountainbiking.net

- resolves to my server and serves correct page

discovermountainbiking.net - resolves to my server and serves apache default page

http://www.absolutelybrilliant.net

- resolves to register4less.com, and it was not registered there and dig shows it resolving to my nameservers.

absolutelybrilliant.net - resolves to my server and serves correct page.

Phew.. I just didn't want to type all of that. Again, sorry for all the typing you did on the wrong addresses.

 

[Trialsman]

I am trying to figure out if there might be something wrong with my resolve.conf file. But I have found nothing about it on any linux documentation site that is any help.

 

[optimised]

Hi Trialsman,
Seams we are having similar problems. I also just installed rh 7.1 ,bind 9.1. Ifincham has indicated that port 53 for dns has some type of filtering going on. Nothing that I set up though. I'm off now trying to figure out if it is being filtered how I can turn filtering off.
I myself have been tinkering with the resolv.conf file to remedy my problem but my problem seems to stem from something else transparet, like a firewall and no other servers see my dns.
If you had any problems with dns port 53 could you let me know how you turned filtering off.

joe