DNS üzerindeki...
 
Bildirimler
Hepsini Temizle

DNS üzerindeki "xxxx.local" kaydı  

  RSS
Tarik ERSOY
(@TarikERSOY)
Üye

Merhabalar,


Asıl sorunum Domain e jonin olamamak. Fakat tüm form ve makaleleri okuyunca muhtemelen sorunun DNS yapılandırmasından kaynaklanabileceğini düşündüm. Formlarda ve makalelerde bahsi geçen tümçözüm önerilerini uygulamama rağmen client lar domain e join olamıyor. Tüm client larda server ulaşılmasına her türlü erişim sağlanmasına rağmen client PC ler domain e katılmaya çalışırken client tan şu mesaj alınıyor ".. istenen işlemi yürütemiyor". Bir test sunucusu kurup orada bir deneme yaptım, ilk seferinde join oldum. Sonra DNS le ilgili bazı düzenlemeler yaptıktan sonra yine join olma sorunu başladı. Domain in AD, Exchange ve DNS aynı server da kurulu.


 Şu an için DNS kayıt durumu resimde görüldüğü gibi. Resimdenda anlayacağınız üzere "teslaxxxxx.local" kaydı bulunmuyor. Normalde DNS i AD ye entegre edilince bu kaydın açılması gerekiyordu ama açılmadı. Şimdiki durumda clientların komut satırından teslaxxxxx domain ismini pingleyemiyorum. Fakat teslaxxxxx.com a ping atabiliyorum. 


1. Join işlemi sırasında domain name e "teslaxxxxx" yazdığımda  user name ve şifre istiyor bunlar girildikten bir süre sonra aşağıdaki hata mesajını veriyor;


"Teslaxxxxx etki alanına katılma girişimi sırasında aşağıdaki hata oluştu.


Belirtilen sunucu istenen işlemi yürütemiyor. "


2. Join işlemi sırasında domain name e "teslaxxxxx.com" yazdığımda direk aşağıdaki hata mesajını veriyor;


"Teslaxxxxx.com etki alanı ile bağlantıya geçilemedi...." 


 


Bu durumda; DNS forvard kayıtlarında teslaxxxxx.local kaydını otomatik oluşturabilirmiyim? eğer artık otomatik oluşamaycak ise manual olarak bu kaydın altında hangi recordlar bulunmalı?


Yardımlarınızı şimdiden teşekkür ederim.


Kolay gelsin. 

Alıntı
Gönderildi : 06/10/2009 20:19
Dogan UZUN
(@doganuzun)
Üye

Merhaba,


dns hata loglarını atabilirsen daha detaylı yardımcı olabiliriz.

CevapAlıntı
Gönderildi : 06/10/2009 23:08
Aykut Sinan ES
(@aykutsinanes)
Üye

Merhaba, DNS uzerinde AD zonunu Olusturuldumu, Yoksa AD yapina Gore Bir PZone Olusturup, DC'ene ait bir HOST A kaydi Olusturman Gerekebilir.


 

CevapAlıntı
Gönderildi : 07/10/2009 02:05
Tarik ERSOY
(@TarikERSOY)
Üye

dns screen


DNS screen i koymayı unutmuşum. DNS konfigürasyonunun son hali bu. (ftp://ftp.teslaelektronik.com/documents/DNSScreen.jpg)


AD zonun dan kastınız .local ise hayır o zone oluşmadı. zaten benim sorunumda bu.


 

CevapAlıntı
Gönderildi : 07/10/2009 02:17
Tarik ERSOY
(@TarikERSOY)
Üye

DNS loglara bu linkten ulaşabilirsiniz ftp://ftp.teslaelektronik.com/documents/DNSLogs.evt

CevapAlıntı
Gönderildi : 07/10/2009 02:25
Dogan UZUN
(@doganuzun)
Üye

Merhaba


Logları kopyalayıp atarmısınız link çalışmıyor.

CevapAlıntı
Gönderildi : 07/10/2009 14:37
Tarik ERSOY
(@TarikERSOY)
Üye

DNS loglarda ortaya çıkan farklı error ve warning kayıtları aşağıda. 


 


Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4004
Date:  06.10.2009
Time:  17:41:06
User:  N/A
Computer: TESLASERVER
Description:
The DNS server was unable to complete directory service enumeration of zone teslaelektronik.com.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Data:
0000: 2a 23 00 00               *#..   


Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date:  06.10.2009
Time:  17:41:06
User:  N/A
Computer: TESLASERVER
Description:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Data:
0000: 51 00 00 00               Q...   


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 414
Date:  06.10.2009
Time:  16:43:33
User:  N/A
Computer: TESLASERVER
Description:
The DNS server machine currently has no DNS domain name.  Its DNS name is a single label hostname with no domain (example:  "host" rather than "host.microsoft.com").
 
You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help.
 
While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname.  This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.
 
To correct this problem:
  1) open Control Panel
  2) open System applet
  3) select Computer Name tab
  4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name
  5) reboot to initialize with new domain name
 
After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name.  However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4521
Date:  06.10.2009
Time:  16:29:39
User:  N/A
Computer: TESLASERVER
Description:
The DNS server encountered error 32 attempting to load zone teslaelektronik.local from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .


Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date:  03.09.2009
Time:  11:46:40
User:  N/A
Computer: TESLASERVER
Description:
DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code.
 
If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
 
If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.
 
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Data:
0000: 2d 23 00 00               -#..   


Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4007
Date:  03.09.2009
Time:  11:03:18
User:  N/A
Computer: TESLASERVER
Description:
The DNS server was unable to open zone _msdcs.teslaltd.teslaelektronikltd.com in the Active Directory from the application directory partition ForestDnsZones.teslaltd.teslaelektronikltd.com. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Data:
0000: 0d 00 00 00               ....   


Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date:  01.09.2009
Time:  13:22:38
User:  N/A
Computer: TESLASERVER
Description:
DNS server has updated its own host (A) records.  In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update.  An error was encountered during this update, the record data is the error code.
 
If this DNS server does not have any DS-integrated peers, then this error
should be ignored.
 
If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.
 
To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact.  (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner.  It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Data:
0000: 2d 23 00 00               -#..   


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date:  20.08.2009
Time:  17:33:02
User:  N/A
Computer: TESLASERVER
Description:
The DNS server encountered a packet addressed to itself on IP address 192.168.122.97. The packet is for the DNS name "_ldap._tcp.pdc._msdcs.teslaltd.teslaelektronikltd.com.". The packet will be discarded. This condition usually indicates a configuration error.
 
Check the following areas for possible self-send configuration errors:
  1) Forwarders list. (DNS servers should not forward to themselves).
  2) Master lists of secondary zones.
  3) Notify lists of primary zones.
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless subzone is also on this server.
  5) Root hints.
 
Example of self-delegation:
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com.
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,
  (bar.example.microsoft.com NS dns1.example.microsoft.com)
  -> BUT the bar.example.microsoft.com zone is NOT on this server.
 
Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result.  If found, the subzone DNS server admin should remove the offending NS record.
 
You can use the DNS server debug logging facility to track down the cause of this problem.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .
Data:
0000: 50 25 00 00               P%..   

CevapAlıntı
Gönderildi : 07/10/2009 15:15
Tarik ERSOY
(@TarikERSOY)
Üye

DNS i silip yeniden yükledim;


Sonra "teslaxxxxx.com" zone unun içe bakan kayıtlarını komple kaldırdım. sadece dışa bakan 81.214.140.xxx leri girdim.


Yeni Bir "Teslaxxxxx.local" zone u oluşturdum. burayada AD olması gereken kayıtlarını girdim.


Birde sadece "teslaxxxxx" isimli zone oluşturdum. buraya default kayıtlar dışında sadece bir A record girdim o da "teslaxxxxx" oldu. Ip olarakta internal ip yi verdim.


fakat hala bir değişiklik olmadı. Teslaxxxxx e (domain name e) ping atamıyorum. Fakat "teslaxxxx.local" "teslaxxxxx.com" lara ping atabiliyorum.


ve hala client ları Domain e katamıyorum.


Acil yardımlarınızı bekliyorum.

CevapAlıntı
Gönderildi : 09/10/2009 18:36
Dogan UZUN
(@doganuzun)
Üye

Forward kısmına 81.214.140......... eklemeyeceksin o kısma telekom dns lerini gireceksin 195.175.39.39   195.175.39.40


 


Kolay Gelsin

CevapAlıntı
Gönderildi : 09/10/2009 22:59
Tarik ERSOY
(@TarikERSOY)
Üye

Forward dan kasınız Forwarders lar ise oraya zaten dış DNS i veriyorum. bahsetiğim 81.214.140.xxx IP ler Forward zone a açtığım "teslaxxxxx.com" zone una ait A recordların IP adresleri. örneğin şirketin www i için girdiğim A record a (www.teslaxxxxx.com) verdiğim IP bizim  sirketin sabit IP si. Forward zone da açtığım diğer kayıt "teslaxxxx.local", buradaki  A recordlarına da içerideki server ların IP lerini (192.168.1.xxx gibi) veriyorum.


 İçerideki clientların (şimdilik workgroup olarak çalışan) isimçözmede herhangi bir sorunu yok. içerideki herhangi bir başka client ı ismi ile ping leyebiliyorlar. DC nin olduğu server ı ismi ile pingleye biliyorlar.Ama iş Domain Name i pinglemeye gelince pingleyemiyoruz. Örneğin exension lı DC adını (teslaxxxx.com) pingleyebiliyorum. Ama Domain adımız olan "TESLAXXXX" i pinglemeye çalıştığım zaman cevap alamıyorum. Okuduğum birkaç makale ve forumda Domain name in pinglenebilmesi gerektiği yazıyor idi.    

CevapAlıntı
Gönderildi : 12/10/2009 02:31
Paylaş: