-
Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.
DNS Server VLAN`s
- Ersteller Andre
- Erstellt am
Hallo
Ich habe zwar meinen DNS Server schon seit Jahren am laufen aber irgendwas ist falsch konfiguriert.
Auf was muss ich beim DNS aufpassen bzw. konfigurieren für mehrere VLANs. ???
Der DHCP von meinen VLAN30 vergibt d. User zwar richtig d. DNS v. VLAN10 aber es funkt einfach nicht.
Vielleicht hat wer einen Tip oder Link für mich.
Danke
Ich habe zwar meinen DNS Server schon seit Jahren am laufen aber irgendwas ist falsch konfiguriert.
Auf was muss ich beim DNS aufpassen bzw. konfigurieren für mehrere VLANs. ???
Der DHCP von meinen VLAN30 vergibt d. User zwar richtig d. DNS v. VLAN10 aber es funkt einfach nicht.
Vielleicht hat wer einen Tip oder Link für mich.
Danke
Hallo Tschuldige
hier meine conf.
notify no;
include "/etc/named.d/forwarders.conf";
};
# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# category lame-servers { null; };
#};
# The following zone definitions don't need any modification. The first one
# is the definition of the root name servers. The second one defines
# localhost while the third defines the reverse lookup for localhost.
zone "." in {
type hint;
file "root.hint";
};
zone "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
# Include the meta include file generated by createNamedConfInclude. This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named
include "/etc/named.conf.include";
logging {
category default { log_syslog; };
channel log_syslog { syslog; };
};
zone "Server" in {
allow-transfer { any; localhost; };
file "master/aet";
type master;
};
zone "domain1.at" in {
allow-transfer { any; localhost; };
file "master/aetgmbh.at";
type master;
};
zone "domain2.at" in {
allow-transfer { any; localhost; };
file "master/kny.at";
type master;
};
zone "10.16.172.in-addr.arpa" in {
allow-transfer { any; localhost; };
file "master/10.16.172.in-addr.arpa";
type master;
};
# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.
hier meine conf.
notify no;
include "/etc/named.d/forwarders.conf";
};
# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
# # Log queries to a file limited to a size of 100 MB.
# channel query_logging {
# file "/var/log/named_querylog"
# versions 3 size 100M;
# print-time yes; // timestamp log entries
# };
# category queries {
# query_logging;
# };
#
# # Or log this kind alternatively to syslog.
# channel syslog_queries {
# syslog user;
# severity info;
# };
# category queries { syslog_queries; };
#
# # Log general name server errors to syslog.
# channel syslog_errors {
# syslog user;
# severity error;
# };
# category default { syslog_errors; };
#
# # Don't log lame server messages.
# category lame-servers { null; };
#};
# The following zone definitions don't need any modification. The first one
# is the definition of the root name servers. The second one defines
# localhost while the third defines the reverse lookup for localhost.
zone "." in {
type hint;
file "root.hint";
};
zone "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
# Include the meta include file generated by createNamedConfInclude. This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named
include "/etc/named.conf.include";
logging {
category default { log_syslog; };
channel log_syslog { syslog; };
};
zone "Server" in {
allow-transfer { any; localhost; };
file "master/aet";
type master;
};
zone "domain1.at" in {
allow-transfer { any; localhost; };
file "master/aetgmbh.at";
type master;
};
zone "domain2.at" in {
allow-transfer { any; localhost; };
file "master/kny.at";
type master;
};
zone "10.16.172.in-addr.arpa" in {
allow-transfer { any; localhost; };
file "master/10.16.172.in-addr.arpa";
type master;
};
# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.
Andre schrieb:
Was funktioniert nicht? Können die User keinen Host bzw. Domainnamen auflösen? Oder werden die PC´s der User nicht im DNS eingetragen?
User können keinen Host bzw. Domainnamen auflösen:
Sind die Server aus VLAN10, per Ping, aus dem VLAN30 erreichbar? Sind die VLAN´s auf dem Switch korrekt getagged?
PC´s werden nicht im DNS eingetragen:
Hast du in deiner DHCP-Konfiguration den Paramater "ddns-updates" auf "on" gesetzt? Wie sehen deine restlichen ddns Parameter aus?
PS:
Du solltest mal das Logging von deinem Bind aktivieren. Logging ist immer sehr hilfreich bei der Fehlersuche.