Delegare subdomenii !?

Salut. Am o problema cu delagarile de subdomenii.

Cazul 1 :
Domeniul este gazduit pe serverul meu de dns
Am domeniul ccitcomputer.ro

cat /var/named/ccitcomputer.ro.zone
$TTL 86400
@       IN      SOA     ns.ccitcomputer.ro.  root.localhost (
                        200403111 ; serial
                        28800 ; refresh
                        7200 ; retry
                        604800 ; expire
                        86400 ; ttl
                        )
        IN      NS      ns.ccitcomputer.ro.
        MX      10      mail.ccitcomputer.ro.
#ns     IN      A       193.231.200.1
ns      IN      A       82.208.174.145
www     IN      CNAME   ns.ccitcomputer.ro.
snmp    IN      CNAME   ns.ccitcomputer.ro.
mail    IN      CNAME   ns.ccitcomputer.ro.
sediu   IN      NS      server.sediu.ccitcomputer.ro.
server.sediu    IN      A       86.34.228.49

La 86.34.228.49 este un router. Am facut forward de port catre server care are ip privat
Acum in subdomeniul sediu.ccitcomputer.ro vreau sa am mx, www, ftp, owa, etc. Unde trebuies declarate, nu pe serverul server.sediu.ccitcomputer.ro ? Eu asa am facut, dar acum am o alta problema cand dau un dig catre www.seiu.ccitcomputer.ro imi apare 10.0.0.254 :), adica adresa interna a serverului , si e clar ca e gresit. Cum fac sa imi apar la aceste inregistrari cu ip-ul extern . Mentionez ca server.sediu.ccitcomputer.ro este 2003 are AD pe el si dns si exchange, etc. Deci trebuie sa raspunda si la interogarile din lan dar si la interogarile din extern.

Caz 2

Domeniu netsafesolutions.ro gazduit la provider. Am cerut sa imi adauge subdomeniul  suport la domeniu si astfel am suport.netsafesolutions.ro. Aici aceasi poveste un 2003 cu ipuri interne. Providerul zice ca desi mi-a facut delegare catre ip public in locatia unde se afala 2003-ul pentru subdomeniu mx-ul si diverse alias-uri trebuiesc facute la el si nu la mine pe server.
Are dreptate ? :cursing: :cursing: :cursing:

C:\Users\cristian.SUPORT>nslookup sediu.ccitcomputer.ro
Server: UnKnown
Address: 192.168.0.1:53

Non-authoritative answer:
Name: sediu.ccitcomputer.ro
Address: 10.0.0.254


mentionez , computerul de pe care am facut interogarea nu este in acel lan, si interogheaza serverele publice ( 192.168.0.1 este serverul dns intern care la randul lui interogeaza serverul providerului.


Asta e la cazul 1 serverul care tine subdomeniul raspunde dar da ip-ul privat . Ceea ce intareste ceea ce stiam serverul delegat se ocupa de obiectele lui, mx-uri si alte alias-uri.
Cum sa fac sai dea si ipul extern prin care iese
Am dat click dreapta pe zona proprietati la name server si l-am editat, unde am adugat si ip-ul public, il ia, dar dupe ce dau reload sau restart zonei, repectivul serverului dns dispare adresa adaugata  <_<

Edited by ceoby, 30 May 2007 - 13:25.

Daca ajuta cu ceva


DNS Report for sediu.ccitcomputer.ro
Generated by www.DNSreport.com at 11:26:58 GMT on 30 May 2007.
Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:

server.sediu.ccitcomputer.ro. [Private IP: 10.0.0.254] [TTL=3600]
[These were obtained from ns.ccitcomputer.ro]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
WARN Glue at parent nameservers WARNING. The parent servers (I checked with ns.ccitcomputer.ro.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.
NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).

http://www.zytrax.co...9/delegate.html

oricum ce incerci tu sa faci acolo, e o mica carpeala. folosesti ip-uri private, publice, port forwarding, etc. nu potate iesi bine din asta. recomandarea mea e sa ai un DNS server extern, care primeste query-urile din exterior, si da raspuns cu adrese publice, si un DNS server intern, in cadrul firmei unde ai record-uri cu ip-uri interne.

Ma , asta e cererea clientului, si eu am vazut solutia asta mergand in mai multe companii.

Am creat un host cu ip public ( tot serverul ns ) la care am creat aliasul www mail si merge si din exterior si din interior, o sa fac acum test sa pun MX

Da, am rezolvat problema  :coolspeak:

Am rezolvat in 2 zile >
Cu varzarii de la ITCNEt care m-au tinut o luna cu delagarea subdomeniului mi-au facut praf pe acolo tot, m-au lasta offline o zi , spunandu-mi ca nu se poate sa 2 servere de mail separate pt 2 subdomenii

Cei de la microsoft nu mi-au raspuns de 2 saptamani sa imi dea o rezolvare, ii cam doare in ..., daca nu ai super contract de suport cu ei. Si asa am fost la un interviu la ei pentruhelp desck si mi-au lasat impresia ca ei stiu mai putin si se bazeaza mai mult pe cei pe care vroiau sa ii angajeze, ce tare, sa vii tu unul sa raspunzi la telefoanele lor sa ii ajuti sa isi administreze ograda, mi s-a parut foarte ciudat, nu facei nici un training, nimic, direct in pine vroiau sa te bage.

Am atasat dedesubt cum arata acum configurata zona pt subdomeniu.

Edited by cristian.ceobanu, 05 June 2007 - 16:20.