Suche

[BlackBoSs]

dieser fehler tratt seit dem auf seit ich den server gewechselt hab !
also mein provider hat mir zugeschlagen das ich nen linux server verwenden soll weil ich nen höheren transfervolumen hab ...
ich hab dann oke gesagt und sie haben nen account bei linux server für mich geöffnet und alle zugangsdaten geschickt ... und ich hab die derzeitige seite ... auf den neuen server hochgeladen und ein backup von der alten seite gemacht und auf den neuen datenbank hochgeladen .. seit dem geht es nicht

[jubilee]

Hallo !
Anscheinend ein fehler in einem DNS-Server
Beim anpingen von www.dermanim.de von BlackBoSs aus bekommt dieser die IP
217.160.204.8
wenn ich von hier aus anpinge bekomm ich
217.160.219.241
Also ist in BlackBosses DNS anscheinend das richtige Zonefile nich nicht geladen. Allerdings hat er den Server schon 48 Std. Eigentlich sollten die DNS schon alle aktualisiert sein ??

[BlackBoSs]

ich hab gerade ne mail an dem provider geschickt ich hoffe ich bekomme ne positive antwort ... wenn nicht werde ich mich hier wieder bei euch um hilfe bitten was ich da so machen könnte
danke nochmals

[munzur]

hi!

bei mir geht sie auch : ping www.dermanim.de -> 217.160.219.241

l.g

[BlackBoSs]

hi hab gestern abend nen mail an mein provider geschickt und habe das bekommen :

  mail from provider :   Sehr geehrter Herr Elvan Dogan,

der DNS Abgleich kann bis zu einer Woche dauern, da es nicht nur einen
DNS-Server auf dieser Welt gibt.

Also abwahrten, bis auch bei allen der DNS-Eintrag dermanim.de und
www.dermanim.de eingetragen wurde.


Für die Beantwortung weiterer Fragen stehen wir Ihnen gerne zur Verfügung.

[BlackBoSs]

aber ich konnte in der schule in die seite rein aber von zuhause kann ich nicht viele können nicht rein

wenn ich ping auf www.dermanim.de mache kommt diese ip 217.160.204.8

aber wenn ich ping auf nur dermanim.de mache kommt diese ip 217.160.219.241

[jubilee]

Hallo !
Du hast doch Antwort von Deinem Provider bekommen.
 

der DNS Abgleich kann bis zu einer Woche dauern, da es nicht nur einen
DNS-Server auf dieser Welt gibt.
Also abwahrten, bis auch bei allen der DNS-Eintrag dermanim.de und
www.dermanim.de eingetragen wurde.
 

Also wart das doch noch ab.
Ich denke es wird in kürze laufen.
MfG
jubilee

[BlackBoSs]

nein nein was ich nicht kapiere ist .. ich hab es in der schule versucht .. es ist gegangen aber von zuhause kann ich nicht

[jubilee]

Hallo !
 

ich hab es in der schule versucht .. es ist gegangen aber von zuhause kann ich nicht
 

Warum ist das so verwunderlich. Jenachdem, über welchen Provider Du dich ins Internet einwählst, ändert sich höchstwahrscheinlich auch der DNS weil viele Dialin-Provider eigene Nameserver betreiben.
Wenn da dann solche Trollos dabei sind, die die Verzonung nur ein mal pro Woche aktualisieren, dann dauerst es halt bis die Adresse richtig gelistet wird.
MfG
jubilee

[BlackBoSs]

von wo habt ihr euren provider ? also host ... ?? ich glaub ihr host ist ganz gut die seite is ganz schnell. sehe nie ein fehler usw.

[jubilee]

Howdi !
Diese Seite ist hier gehostet :
 http://www.power-maax.de/
MfG
jubilee.

[munzur]

Howdi !
Diese Seite ist hier gehostet :
 http://www.power-maax.de/
MfG
jubilee.

 

hi!

ich würd gern was von euch nehmen aber ihr seids zu teuer  

ich suche einen DedizierteServer aber bei euch ist der billigste 129 € im monat + inst. gebühr von 99 €! und nur mit 5GB Traffic <- wenig!

Da gibt es bessere Angebote! Muss nur sagen das, dass für Deutsche Angebote zu Teuer ist!

Kann sein das ihr auch sehr viele Vorteile habt, aber ka welche!


DAnke

[jubilee]

Hallo !
 

Da gibt es bessere Angebote! Muss nur sagen das, dass für Deutsche Angebote zu Teuer ist!
 

Ich sag mal "günstigere Angebote".
Ob die besser sind, muss dan jeder für sich entscheiden.
Z.B. einen Linux-Server z.B. bei 1&1/strato/server4you zu bestellen OHNE jedliche Erfahrung in
Linux mag günstiger sein. Mit Sicherheit (oder ohne dieselbe ) ist es jedenfalls schon fast fahrlässig.
Ich administrier selbst einen Server und ich kann ungefähr abschätzen, was es an Zeit und Arbeit kostet, wenn man keinen 1a Service im Hintergrund hat.
Wie gesagt, jeder bekommt das wofür er zahlen will.
MfG
jubilee



[Editiert am 21/4/2004 von jubilee]

[BlackBoSs]

DNS Report for dermanim.de
Generated by www.DNSreport.com at 15:47:47 GMT on 22 Apr 2004.
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.
 
WARN
 NS records at parent servers
 Your NS records APPEAR to be:

ns.webnetpc.net. [217.160.208.75] [TTL=604800] [DE]
ns.schlund.de. [195.20.224.97] [TTL=604800] [DE]
NOTE: These records may be inaccurate, since the parent servers (i.de.net.) do not know the NS records for dermanim.de (or give a referral to other DNS servers)! This may cause other tests not to work properly, such as the 'Nameservers on separate class C' test.
 
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, with 2 entries.
 
PASS
 Glue at parent nameservers
 OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
 

 

NS
 INFO
 NS records at your nameservers
 Your NS records at your nameservers are:

ns.webnetpc.net. [TTL=604800]
ns.schlund.de. [TTL=604800]
 
PASS
 All nameservers report identical NS records
 OK. The NS records at all your nameservers are identical.
 
PASS
 All nameservers respond
 OK. All of your nameservers listed at the parent nameservers responded.
 
PASS
 Nameserver name validity
 OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
 
PASS
 Number of nameservers
 OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
 
PASS
 Lame nameservers
 OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
 
PASS
 Missing (stealth) nameservers
 OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
 
PASS
 Missing nameservers 2
 OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.
 
PASS
 No CNAMEs for domain
 OK. There are no CNAMEs for dermanim.de. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Note that I only checked dermanim.de, I did not check the NS records, which should not have CNAMEs either.
 
PASS
 No NSs with CNAMEs
 OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
 
PASS
 Nameservers on separate class C's
 OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.
 
PASS
 All NS IPs public
 OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
 
INFO
 Nameservers versions
 Your nameservers have the following versions:

217.160.208.75: "9.1.3"
195.20.224.97: No version info available (refused).
 
PASS
 NS TTL discrepancy
 OK. Your NS records at your authoritative DNS servers have TTLs that match those of the parent servers. This is prevents some odd problems that could otherwise occur.
 
PASS
 Stealth NS record leakage
 Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.
 

 

SOA
 INFO
 SOA record
 Your SOA record [TTL=604800] is:

Primary nameserver: ns.webnetpc.net.
Hostmaster E-mail address: webhoster.dermanim.de.
Serial #: 2004022502
Refresh: 28800
Retry: 7200
Expire: 604800
Default TTL: 39600
 
PASS
 NS agreement on SOA serial #
 OK. All your nameservers agree that your SOA serial number is 2004022502. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS Report only checks the NS records listed at the parent servers (not any stealth servers).
 
PASS
 SOA MNAME Check
 OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns.webnetpc.net.. That server is listed at the parent servers, which is correct.
 
PASS
 SOA RNAME Check
 OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: webhoster@dermanim.de. (techie note: we have changed the initial '.' to an '@' for display purposes).
 
PASS
 SOA Serial Number
 OK. Your SOA serial number is: 2004022502. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
 
WARN
 SOA REFRESH value
 WARNING: Your SOA REFRESH interval is : 28800 seconds. This seems a bit high. You should consider decreasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours; 12 hours seems very high to us), although some registrars may limit you to 10000 seconds or higher, and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommend 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time.
 
PASS
 SOA RETRY value
 OK. Your SOA RETRY interval is : 7200 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
 
PASS
 SOA EXPIRE value
 OK. Your SOA EXPIRE time: 604800 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
 
PASS
 SOA MINIMUM TTL value
 OK. Your SOA MINIMUM TTL is: 39600 seconds. This seems normal (about 60 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
 

 

MX
 INFO
 MX Record
 Your 1 MX record is:
50 mail.dermanim.de. [TTL=604800] IP=217.160.219.241 [TTL=604800] [DE]
 
PASS
 Invalid characters
 OK. All of your MX records appear to use valid hostnames, without any invalid characters.
 
PASS
 All MX IPs public
 OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
 
PASS
 MX records are not CNAMEs
 OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
 
PASS
 MX A lookups have no CNAMEs
 OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
 
PASS
 MX is host name, not IP
 OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
 
WARN
 Multiple MX records
 WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.
 
PASS
 Duplicate MX records
 OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
 
PASS
 Reverse DNS entries for MX records
 OK. The IPs of all of your mail server(s) have reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. The reverse DNS entries are:

241.219.160.217.in-addr.arpa sv5-webnetpc.de. [TTL=86400]
 

 

Mail
 PASS
 Connect to mail servers
 OK: I was able to connect to all of your mailservers.
 
WARN
 Mail server host name in greeting
 WARNING: One or more of your mailservers may be claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). This probably won't cause any harm, but may be a technical violation of RFC821 4.3 (and RFC2821 4.3.1).

mail.dermanim.de claims to be host p15150050.pureserver.info.
 
PASS
 Acceptance of NULL <> sender
 OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).
 
FAIL
 Acceptance of postmaster address
 ERROR: One or more of your mailservers does not accept mail to postmaster@dermanim.de. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.

mail.dermanim.de's postmaster response:
    >>> RCPT TO:<postmaster@dermanim.de>
    <<< 550 : User unknown
 
WARN
 Acceptance of abuse address
 WARNING: One or more of your mailservers does not accept mail to abuse@dermanim.de. Mailservers are expected by RFC2142 to accept mail to abuse.

mail.dermanim.de's abuse response:
    >>> RCPT TO:<abuse@dermanim.de>
    <<< 550 : User unknown
 
PASS
 Acceptance of domain literals
 OK: All of your mailservers accept mail in the domain literal format (user@[217.160.219.241]).
 
PASS
 Open relay test
 OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.
mail.dermanim.de OK: 554 : Relay access denied
 

 

WWW
 INFO
 WWW Record
 Your www.dermanim.de A record is:

www.dermanim.de.  A  217.160.219.241 [TTL=604800] [DE]
 
PASS
 All WWW IPs public
 OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.
 
PASS
 CNAME Lookup
 OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.dermanim.de, which is good.
 



Legend:

Rows with a FAIL indicate a problem that in most cases really should be fixed.
Rows with a WARN indicate a possible minor problem, which often is not worth pursuing.

CNAME Lookup
 OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.dermanim.de, which is good.
 



Legend:

Rows with a FAIL indicate a problem that in most cases really should be fixed.
Rows with a WARN indicate a possible minor problem, which often is not worth pursuing.

#


das hat mir mein provider geschickt aber die seite funkt trotzdem ned

[munzur]

versuch mal das bin neugierig

vkpMx 2.x - Webserver-Testtool
 http://www.pragmamx.org/modules.php?name=Downloads&d_op=getit&lid=304

[BlackBoSs]

testtool ? das hat da jubilee eh schon ganz am anfang gemacht !
funkt alles