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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi, I've been browsing past posts here, and I have to say this place it's great! That guy who doesn't like ICQ it's a very generous person, giving his expertise and knowledge to others. Thanks a lot.
I'm new to linux, and it took me several weeks to make this thing working.
I'm running a server in order to be mailserver, DNS server and proxy server. For now, my mail server is running fine and DNS .... I'm not quite sure. I can send and receive messages, but sending them from some places work, but from other they doesn't. The DNS server name is ns1.setecsa.com and it was registered as primary name server with netsol. Mail server is mail.setecsa.com, and if you use a POP mail (web based) retreiver, it works perfect. But, if you try to ping, traceroute, or any attempt to resolve names on my domain (setecsa.com), they fail. Wrong IP to mail.setecsa.com, or similar messages. I called my ISP (I have 6 public IP's) and asked them about it, and they said something about not being able to use ns1.setecsa.com as a nameserver, as its IP address is already registered as setecsa6.att.net.co
My question is: Should I register setecsa6.att.ent.co as nameserver with netsol, or what should I do? What might be the problem? What am I missing here, or what am I doing wrong?
I know something's right since I'm able to receive mail under my domain name (if you want to test it, please send me a mail to test@setecsa.com), but something's wrong since some mailers doesn't see my server.
I can send you my config files for named if you want them. Or any test, config file, etc you might want to see. I'm running RedHat 7.1
Thanks a lot
Rafael
PS.
On another related mail topic, if it's OK if I read POP mails using PINE, and other mail programs, like Eudora? (Newbiest question)
Don't know whats wrong with the registration, but I don't get any valid Whois/RIPE/ARIN response for the att.co address.
OTOH, I do get response on ns1:
Hostname: ns1.setecsa.com
IP Address: 200.74.133.158
registered for SEGURIDAD TECNICA S.A.
Even if the DNS was setecsa6.att.net.co your ISP should be able to make an alias "ns1.setecsa.com" pointing to setecsa6.att.net.co .
Now im querying nameservers for setecsa.com, and I get:
ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
setecsa.com, type = NS, class = IN
ANSWER SECTION:
setecsa.com. 23h49m3s IN NS localhost.
setecsa.com. 23h49m3s IN NS ns1.
and for the MX records:
ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
setecsa.com, type = MX, class = IN
ANSWER SECTION:
setecsa.com. 1D IN MX 10 mail.setecsa.com.
(etc additional records)
So it says "the domain setecsa.com is referenced in the nameserver localhost, and in the nameserver ns1 (of the domain) (what? where? where can I find that DNS?).
IIRC (and Im no DNS guru) the SOA record maybe missing A records, because we do not get shown canonical name to address(IP) mapping (the "IN A" part in the SOA?).
Thanks for replying guys, here you can see my named config files. Hope you can find what I'm missing here.
Thanks in advance,
Rafael
This is 0.0.127.in-addr.arpa.zone:
$TTL 86400
@ IN SOA localhost. root.localhost (
2 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttk
)
@ IN NS localhost.
@ IN NS trinity.attla.net.co.
1 IN PTR localhost.
This is localhost.zone
$TTL 86400
@ IN SOA @ root.localhost (
2 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)
@ IN NS localhost.
@ IN NS trinity.attla.net.co
@ IN MX 10 mail.setecsa.com
@ IN A 127.0.0.1
This is setecsa.com.zone
$TTL 86400
@ IN SOA ns1.setecsa.com. root.localhost (
3 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)
ns1 IN NS trinity.attla.net.co
@ IN NS localhost.
@ IN NS ns1.
ns1 IN NS ns1.granitecanyon.com
ns1 IN NS ns2.granitecanyon.com
@ IN MX 10 mail.setecsa.com.
mail IN MX 10 mail
ns1 IN A 200.74.133.158
mail IN A 200.74.133.157
@ IN A 200.74.133.158
localhost IN A 127.0.0.1
www IN A 200.31.22.44
This is 133.74.200.in-addr.arpa.zone
$TTL 86400
@ IN SOA ns1.setecsa.com. root.localhost (
2 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttk
)
@ IN NS ns1.
@ IN NS ns1.setecsa.com.
@ IN NS trinity.attla.net.co.
157 IN PTR mail.setecsa.com.
158 IN PTR ns1.setecsa.com.
This is named.local
$TTL 86400
@ IN SOA localhost. root.localhost. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS localhost.
Originally posted by rebayona
This is setecsa.com.zone
$TTL 86400
@ IN SOA ns1.setecsa.com. root.localhost (
3 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)
ns1 IN NS trinity.attla.net.co
@ IN NS localhost.
@ IN NS ns1.
ns1 IN NS ns1.granitecanyon.com
ns1 IN NS ns2.granitecanyon.com
@ IN MX 10 mail.setecsa.com.
mail IN MX 10 mail
ns1 IN A 200.74.133.158
mail IN A 200.74.133.157
@ IN A 200.74.133.158
localhost IN A 127.0.0.1
www IN A 200.31.22.44
I feel a bit confused about this part: ns1 IN NS trinity.attla.net.co
@ IN NS localhost.
@ IN NS ns1.
ns1 IN NS ns1.granitecanyon.com
ns1 IN NS ns2.granitecanyon.com
If I'm reading it correctly it says that trinity.attla.net.co.setecsa.com is responsible for the domain ns1.setecsa.com
Every dns name in the zone files are added to the current domain unless they are ended with a .(dot)
If you look at your MX record it ends with a dot @ IN MX 10 mail.setecsa.com.
I think your nameserver records should look like this @ IN NS trinity.attla.net.com.
@ IN NS localhost.
@ IN NS ns1.
@ IN NS ns1.granitecanyon.com.
@ IN NS ns2.granitecanyon.com.
@ stands for the zone name given in the /etc/named.conf file, in your case probably setecsa.com
Please make backup copies of config files before tampering, I'm pretty new to DNS and bind.
nslookup is a tools for querying DNS servers, it can run in two different modes, command line or interractive.
nslookup without parameters enters interactive mode.
When nslookup is started you can querry some of your machines registered in dns file by entering their dns name and hit enter. To check the .in.addr.arpa give ip number of a host and nslookup will try to resolve the dns name.
Ooops forgot to tell you to increment the serial number in any dns-file you edit or else dns servers doesn't know anything is modified.
XXX.att.net.co it's OK, but it should have been resolved as ns1.setecsa.com instead. Should I ask att (my ISP) to add an "A" registry in their DNS pointing that IP to ns1.setecsa.com ? Or, as I manage my DNS indepently from them, should I do something different?
I have tried to check the dns servers mentioned in your dns configuration.
Only one of them seems to work, ns1.granitecanyon.com
Both attla.net and ns2.granitecanyon.com doesn't resolve your dns name.
This is what I get from ns1.granitecanyon.com:
Code:
> ls setecsa.com
[[205.166.226.38]]
setecsa.com. NS server = ns1.setecsa.com.setecsa.com
setecsa.com. NS server = localhost
setecsa.com. A 200.74.133.158
mail A 200.74.133.157
localhost A 127.0.0.1
www A 200.31.22.44
ns1 NS server = ns1.granitecanyon.com
ns1 NS server = ns2.granitecanyon.com
ns1 NS server = trinity.attla.net.co
> setecsa.com
Server: [205.166.226.38]
Address: 205.166.226.38
Name: setecsa.com
Address: 200.74.133.158
It looks like you have missed a trailing dot somewhere in setecsa.com.zone file. Apart from this problem there seems to be some problem with the other name servers, don't know what.
I tried to use your dns but can't reach it. Seems like your ISP didn't put your name server ip (200.74.133.158) in the in.addr-arpa file.
www server ip (200.31.22.44) seems missing to.
This is what I can come up to now, check with your ISP regarding your ip addresses and what they have put in the configs.
Hi, I just wanted to share that the problem is history now. (At least this is what I think, feel free to check). My ISP was the cause of the problem: They had to change the assigned name they had for that IP to the name I put to it, and that was it! (like unSpawn pointed)
i am runing Fedora2 Server; i configured DNS for LAN but it's working now.
IP eht0: inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0
Gateway IP Add : 192.168.0.254
options {
directory "/var/named";
pid-file "/var/run/named/named.pid";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source address * port 53;
};
1 IN PTR linux.hxanh.net.
2 IN PTR mail.hxanh.net.
3 IN PTR www.hxanh.net.
12 IN PTR pc12.hxanh.net.
5 IN PTR pc5.hxanh.net.
82 IN PTR pc82.hxanh.net.
15.0.168.192.in-addr.arpa. IN PTR pc15.hxanh.net.
200.0.168.192.in-addr.arpa. IN PTR dhcp200.hxanh.net.
201.0.168.192.in-addr.arpa. IN PTR dhcp201.hxanh.net.
202.0.168.192.in-addr.arpa. IN PTR dhcp202.hxanh.net.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.