configuraciones DNS

el
Hoy por la manaña, al llegar al trabajo y checar como amanecio el servidor de correos, me doy cuenta que hay 25 correos por entregar.. A chispas, otro usuario tratando de enviar correos de mas de 11 megas con su poderoso "outluc", o tal vez una famosa cadena de las que acostumbran enviar los de "ventas". No, esta vez se trataba de algo un tanto distinto, las mismas cadenas y correitos basura y quita-tiempo de siempre, pero este caso el error era algo mas extraño como el dominio extraño "pinguilolo.com.mx"

al ver que el sendmail nomas no encontraba ese dominio, pues a hacerle un dig o un host y "O sorpresa":

dns1:~ # host pinguilolo.com.mx
pinguilolo.com.mx has address 192.168.0.35
dns1:~ #

pense que tal vez el servidor dns (bind/named) le habia ocurrido algo, pero la probarlo desde mi casa

persa@persepolis:~> host -v pinguilolo.com.mx
Trying "pinguilolo.com.mx"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38065
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;pinguilolo.com.mx. IN A

;; ANSWER SECTION:
pinguilolo.com.mx. 85985 IN A 192.168.0.35

Received 51 bytes from 200.33.146.209#53 in 828 ms
persa@persepolis:~>

al probar con The DNS Sleuth

Check results for pinguilolo.com.mx

Starting zone checks for pinguilolo.com.mx
Checking zone name
Checking existence of zone
Checking NS records 

    -> pinguilolo.com.mx. 86400 IN NS dns.satinet.com.mx.
### Error: Each domain should have at least 2 nameservers [see RFC1912:2.8 for details]
Checking nameserver authority and synchronization 
    -> dns.satinet.com.mx. 86400 IN A 200.76.65.37
### Error: Unable to resolve 37.65.76.200.in-addr.arpa.: SERVFAIL
### Error: dns.satinet.com.mx (200.76.65.37) has no reverse record [see RFC1912:2.1 for details]
Probing name server dns.satinet.com.mx (200.76.65.37)
Decided to use dns.satinet.com.mx (200.76.65.37) for zone check
Checking whether dns.satinet.com.mx knows an A record for its own name
Checking whether dns.satinet.com.mx is able to reverse-map its own IP address
Checking connectivity with other nameservers
Checking mapping of localhost
Fetching zone data for pinguilolo.com.mx
Parsing zone data
Checking consistency of zone records 
    pinguilolo.com.mx. 86400 IN NS dns.satinet.com.mx.
   pinguilolo.com.mx. 86400 IN MX 10 mail.pinguilolo.com.mx.
   -> mail.pinguilolo.com.mx. 86400 IN A 192.168.0.35
### Warning: Private addresses shouldn't occur in public zones [see RFC1918 for details]
### Error: mail.pinguilolo.com.mx (192.168.0.35) has no reverse record [see RFC1912:2.1 for details] 
    pinguilolo.com.mx. 86400 IN SOA dns.satinet.com.mx. jlsuarez.satinet.com.mx. (
     2005102001 ; Serial
     28800 ; Refresh
     14400 ; Retry
     3600000 ; Expire
     86400 ) ; Minimum TTL
Hostmaster e-mail address is jlsuarez@satinet.com.mx 
    -> satinet.com.mx. 86400 IN MX 10 mail.satinet.com.mx.
   -> mail.satinet.com.mx. 86400 IN A 200.76.65.37
### Warning: Expire time should be between 2 and 4 weeks [see RFC1912:2.2 for details] 
    pinguilolo.com.mx. 86400 IN A 192.168.0.35
   ftp.pinguilolo.com.mx. 86400 IN A 192.168.0.35
   mail.pinguilolo.com.mx. 86400 IN A 192.168.0.35
   www.pinguilolo.com.mx. 86400 IN A 192.168.0.35
Summary: 4 errors, 2 warnings


pues si, una mala configuración :P al menos los correos no eran tan importantes, ya esta como el hacker que ataco 127.0.0.1 :P

Comentarios

Publicar un comentario