telnet pop3.rwhdesign.co.uk 110
user chrissie@rwhdesign.co.uk
pass
L2a8cxId
list
user chrissie@rwhdesign.co.uk
+ OK Password required.
pass L2a8cxId
+OK logged in.
list
+OK POP3 clients that break here, they violate STD53.
1 5532
2 3216
3 3205
4 6729
secedit /refreshpolicy machine_policy /enforce
DNS
Address (A) Record
1. TTL: This is the Time To Live for this record, in seconds. Any Server which once queries this record will update this record after this time interval. The ideal TTL is 86400, which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
2. MX Priority: An MX Record has a Preference number indicating the order in which the mail server should be used (only relevant when multiple MX Records are defined for the same domain name). Mail servers will attempt to deliver mail to the server with the lowest preference number first, and if unsuccessful, continue with the next lowest and so on.
CNAME Record
Host Name: If you wish to Add a CNAME Record for yourdomainname.com like manage.yourdomainname.com or www.yourdomainname.com, then enter the Host Name as manage or www in this text box
All DNS records have a TTL property, specifying the maximum amount of time other DNS servers and applications should cache the record.
Setting a DNS record’s TTL value to zero, means that applications and DNS servers should not cache the record.
When a DNS record is stored in the cache of a DNS server, the record’s TTL is continuously reduced as time go by, and when the TTL finally reaches zero the record is removed from the cache.
When a DNS server passes DNS records from the cache along to applications and other DNS servers, it supplies the current TTL value – not the original. This way the original TTL is guaranteed no matter how many DNS servers the record passes through.
When deciding on the TTL, you need to consider how often the record will be changed.
Because of caching, changes to a DNS record will not reach the entire network until the original TTL has expired – a good reason for setting a short TTL.
However caching helps reduce network traffic. The longer the TTL, the longer the record will live in other DNS server caches around the world, and so fewer requests to the original DNS server are needed – a good reason for setting a long TTL.
Generally, for a record pointing to a server/device with a static IP address and no need for quick updates, a TTL of one day is a good starting point.
However, if the record is for a host with a dynamic IP address or for server which is part of a failover set (see http://www.simplefailover.com), you should be using a TTL value of a few minutes or less.
Active Directory FSMO Roles
In a forest, there are at least five FSMO roles that are assigned to one or more domain controllers. The five FSMO roles are:
Transfer the Schema Master Role
Use the Active Directory Schema Master snap-in to transfer the schema master role. Before you can use this snap-in, you must register the Schmmgmt.dll file.
Register Schmmgmt.dll
Transfer the Schema Master Role
PDC Emulator: The PDC emulator is a domain controller that advertises itself as the primary domain controller (PDC) to workstations, member servers, and domain controllers that are running earlier versions of Windows. For example, if the domain contains computers that are not running Microsoft Windows XP Professional or Microsoft Windows 2000 client software, or if it contains Microsoft Windows NT backup domain controllers, the PDC emulator master acts as a Windows NT PDC. It is also the Domain Master Browser, and it handles password discrepancies. At any one time, there can be only one domain controller acting as the PDC emulator master in each domain in the forest.