Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have done like this is it ok.I have registered my domain in godaddy.com.whether i have to buy a nameserver. i have changed in the nameserver field to ns1.indyablog.com.Plz dont mistake me as im keep on asking questions.
Read what I posted back in reply number 13. You do not have things set up well, and it isn't a DNS problem anymore, it is the way you did the virtual hosts.
Dear Jim
Dont mistake me as if im keep on asking questions.Im in a pressure to finish this job.
I need to run my mail server first.I dont want 2 virtual server,later i will work on it.For that how to configure Http file. I have register my domain in godaddy.com. i have changed my nameserver to ns1.indyablog.com. Whether i hav to buy a own name server since i simply changed to ns1.indyablog.com. or by buying the domain itself they will provide us a nameserver i dunno.tell me.
Thanks
jim@jimsworktop:~$ dig ns1.indyablog.com +trace
; <<>> DiG 9.4.2 <<>> ns1.indyablog.com +trace
;; global options: printcmd
. 351236 IN NS g.root-servers.net.
. 351236 IN NS c.root-servers.net.
. 351236 IN NS m.root-servers.net.
. 351236 IN NS k.root-servers.net.
. 351236 IN NS j.root-servers.net.
. 351236 IN NS b.root-servers.net.
. 351236 IN NS i.root-servers.net.
. 351236 IN NS h.root-servers.net.
. 351236 IN NS e.root-servers.net.
. 351236 IN NS d.root-servers.net.
. 351236 IN NS f.root-servers.net.
. 351236 IN NS a.root-servers.net.
. 351236 IN NS l.root-servers.net.
;; Received 388 bytes from 192.168.68.103#53(192.168.68.103) in 3 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 495 bytes from 199.7.83.42#53(l.root-servers.net) in 92 ms
ns1.indyablog.com. 172800 IN A 220.227.28.84
indyablog.com. 172800 IN NS ns1.indyablog.com.
indyablog.com. 172800 IN NS ns2.indyablog.com.
;; Received 115 bytes from 192.41.162.30#53(l.gtld-servers.net) in 21 ms
jim@jimsworktop:~$ dig ns2.indyablog.com +trace
; <<>> DiG 9.4.2 <<>> ns2.indyablog.com +trace
;; global options: printcmd
. 351228 IN NS m.root-servers.net.
. 351228 IN NS a.root-servers.net.
. 351228 IN NS e.root-servers.net.
. 351228 IN NS g.root-servers.net.
. 351228 IN NS l.root-servers.net.
. 351228 IN NS f.root-servers.net.
. 351228 IN NS c.root-servers.net.
. 351228 IN NS j.root-servers.net.
. 351228 IN NS k.root-servers.net.
. 351228 IN NS d.root-servers.net.
. 351228 IN NS i.root-servers.net.
. 351228 IN NS h.root-servers.net.
. 351228 IN NS b.root-servers.net.
;; Received 388 bytes from 192.168.68.103#53(192.168.68.103) in 2 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 495 bytes from 193.0.14.129#53(k.root-servers.net) in 87 ms
ns2.indyablog.com. 172800 IN A 220.227.28.84
indyablog.com. 172800 IN NS ns1.indyablog.com.
indyablog.com. 172800 IN NS ns2.indyablog.com.
;; Received 115 bytes from 192.52.178.30#53(k.gtld-servers.net) in 109 ms
That means godaddy has the correct info about the IP address of your server. Now you aren't giving out answers, so your DNS config is either not running, or misconfigured:
As to the website, there is no problem with running virtual servers. Most people do. But I have been telling you since post 13 what is wrong, and you don't bother to read it. You asked for an explanation, and I provided it, yet you still didn't set it up like I told you. I am through helping you. Since you think you are in a hurry, I suggest you seek out somebody with a higher skill level than you have at present, and pay them to set things up for you.
As others have pointed out... your name server does not understand that it is the SOA for indyablog.com. Thus, its not going to return any answers for indyablog.com. This is no doubt a configuration problem with your zone file -or- you are not loading the zone in named.conf.
Long pause....
Did you know your name server is answering DNS requests for other domain names. This problem should be fixed as well in named.conf -once- you resolve the SOA problem for indyablog.com. e.g. recursion settings.
Suggestion:
Use command "named-checkzone" to test your zone file changes. I had to make some simple changes to your zone file to get the zone to load properly. hint: indentations <tab> for continuation lines from SOA entry.
Also, don't let the following side-track your efforts in fixing the above problems first... but since you are going to admin a public name server, I would strongly suggest that you secure your configuration using the following template. This is the template I use for all my name servers configurations.
The thing is the names are resolving,but if u type www.mail.indyablog.com in ur browser it wont display anything.You add 202.138.96.3 in your alternated DNS section and try to browse www.mail.indyablog.com.it will work. i dunno y is it so?
The thing is the names are resolving,but if u type www.mail.indyablog.com in ur browser it wont display anything.You add 202.138.96.3 in your alternated DNS section and try to browse www.mail.indyablog.com.it will work. i dunno y is it so?
Your domain registration is currently pointed to your name server at 220.227.28.84. But 202.138.96.3 is answering authoritatively for indyablog.com. Another oddity is when you query this server, it says 202.138.96.2 is the correct IP address. You really need to work out what DNS server(s) will be the start of authority for your domain. Do not pass go, do not collect $200.00. GET THIS WORKED OUT!!!!
Also, if you are in such a hurry, then why don't you just change your domain registration to use the other DNS servers (see below). They are at least answering correctly.
Code:
[scowles@excelsior ~]$ dig @202.138.96.2 indyablog.com soa
; <<>> DiG 9.3.4 <<>> @202.138.96.2 indyablog.com soa
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51695
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;indyablog.com. IN SOA
;; ANSWER SECTION:
indyablog.com. 86400 IN SOA murnsp001.rilinfo.net.
hostmaster.rilinfo.net. 2007122725 28800 7200 604800 86400
;; AUTHORITY SECTION:
indyablog.com. 86400 IN NS ns2.rilinfo.net.
indyablog.com. 86400 IN NS ns1.rilinfo.net.
;; ADDITIONAL SECTION:
ns1.rilinfo.net. 86400 IN A 202.138.96.2
ns2.rilinfo.net. 86400 IN A 202.138.103.100
;; Query time: 283 msec
;; SERVER: 202.138.96.2#53(202.138.96.2)
;; WHEN: Mon Dec 31 15:50:46 2007
;; MSG SIZE rcvd: 167
[scowles@excelsior ~]$ dig @202.138.103.100 indyablog.com soa
; <<>> DiG 9.3.4 <<>> @202.138.103.100 indyablog.com soa
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13093
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;indyablog.com. IN SOA
;; ANSWER SECTION:
indyablog.com. 86400 IN SOA murnsp001.rilinfo.net.
hostmaster.rilinfo.net. 2007122725 28800 7200 604800 86400
;; AUTHORITY SECTION:
indyablog.com. 86400 IN NS ns2.rilinfo.net.
indyablog.com. 86400 IN NS ns1.rilinfo.net.
;; ADDITIONAL SECTION:
ns1.rilinfo.net. 86400 IN A 202.138.96.2
ns2.rilinfo.net. 86400 IN A 202.138.103.100
;; Query time: 300 msec
;; SERVER: 202.138.103.100#53(202.138.103.100)
;; WHEN: Mon Dec 31 15:53:25 2007
;; MSG SIZE rcvd: 167
[scowles@excelsior ~]$ dig @202.138.96.3 mail.indyablog.com a
; <<>> DiG 9.3.4 <<>> @202.138.96.3 mail.indyablog.com a
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1244
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;mail.indyablog.com. IN A
;; ANSWER SECTION:
mail.indyablog.com. 86400 IN A 220.227.28.84
;; AUTHORITY SECTION:
indyablog.com. 86400 IN NS ns2.rilinfo.net.
indyablog.com. 86400 IN NS ns1.rilinfo.net.
;; ADDITIONAL SECTION:
ns1.rilinfo.net. 86400 IN A 202.138.96.2
ns2.rilinfo.net. 86400 IN A 202.138.103.100
;; Query time: 284 msec
;; SERVER: 202.138.96.3#53(202.138.96.3)
;; WHEN: Mon Dec 31 16:06:22 2007
;; MSG SIZE rcvd: 131
[scowles@excelsior ~]$ dig @202.138.96.3 indyablog.com MX
; <<>> DiG 9.3.4 <<>> @202.138.96.3 indyablog.com MX
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4982
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; QUESTION SECTION:
;indyablog.com. IN MX
;; ANSWER SECTION:
indyablog.com. 86400 IN MX 10 mail.indyablog.com.
;; AUTHORITY SECTION:
indyablog.com. 86400 IN NS ns2.rilinfo.net.
indyablog.com. 86400 IN NS ns1.rilinfo.net.
;; ADDITIONAL SECTION:
mail.indyablog.com. 86400 IN A 220.227.28.84
ns1.rilinfo.net. 86400 IN A 202.138.96.2
ns2.rilinfo.net. 86400 IN A 202.138.103.100
;; Query time: 283 msec
;; SERVER: 202.138.96.3#53(202.138.96.3)
;; WHEN: Mon Dec 31 16:06:32 2007
;; MSG SIZE rcvd: 147
#### www.mail.indyablog.com is not working NXDOMAIN ####
[scowles@excelsior ~]$ dig @202.138.96.3 www.mail.indyablog.com a
; <<>> DiG 9.3.4 <<>> @202.138.96.3 www.mail.indyablog.com a
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42753
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.mail.indyablog.com. IN A
;; AUTHORITY SECTION:
indyablog.com. 86400 IN SOA murnsp001.rilinfo.net.
hostmaster.rilinfo.net. 2007122725 28800 7200 604800 86400
;; Query time: 283 msec
;; SERVER: 202.138.96.3#53(202.138.96.3)
;; WHEN: Mon Dec 31 15:59:24 2007
;; MSG SIZE rcvd: 108
BTW: www.mail.indyablog.com would require you to configure a sub-domain (mail.indablog.com) with its own start of authority delegation records and zone files. Are you sure this is how you want to reference your website?
Jan 3 11:23:38 mail named[4325]: starting BIND 9.2.4 -u named -t /var/named/chroot
Jan 3 11:23:38 mail named[4325]: using 1 CPU
Jan 3 11:23:38 mail named: named startup succeeded
Jan 3 11:23:38 mail named[4325]: loading configuration from '/etc/named.conf'
Jan 3 11:23:38 mail named[4325]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 3 11:23:38 mail named[4325]: listening on IPv4 interface eth0, 192.168.1.231#53
Jan 3 11:23:38 mail named[4325]: command channel listening on 127.0.0.1#953
Jan 3 11:23:38 mail named[4325]: zone 0.in-addr.arpa/IN: loaded serial 42
Jan 3 11:23:38 mail named[4325]: zone 1.168.192.in-addr.arpa/IN: loaded serial 2008030101
Jan 3 11:23:38 mail named[4325]: zone 255.in-addr.arpa/IN: loaded serial 42
Jan 3 11:23:38 mail named[4325]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
Jan 3 11:23:38 mail named[4325]: zone mail.indyablog.com/IN: loaded serial 2008010201
Jan 3 11:23:38 mail named[4325]: zone localdomain/IN: loaded serial 42
Jan 3 11:23:38 mail named[4325]: running
Jan 3 11:23:38 mail named[4325]: zone 1.168.192.in-addr.arpa/IN: sending notifies (serial 2008030101)
Jan 3 11:23:38 mail named[4325]: zone mail.indyablog.com/IN: sending notifies (serial 2008010201)
Jan 3 11:23:39 mail named[4325]: lame server resolving 'ns2.indyablog.com' (in 'indyablog.com'?): 220.227.28.84#53
Jan 3 11:23:39 mail named[4325]: lame server resolving 'ns2.indyablog.com' (in 'indyablog.com'?): 220.227.28.84#53
Jan 3 11:24:38 mail named[4325]: received notify for zone '1.168.192.in-addr.arpa'
Jan 3 11:24:39 mail named[4325]: received notify for zone 'mail.indyablog.com'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.